Info Panel Issues

Is there a known bug (with update/fix) in CS6 as to why sometimes my info panel displays color values and sometimes it doesn't?

I haven't done anything other than add my footage to the timeline. I have 2 layers (1 targa seq and 1 png seq). As I move my mouse from the Timeline to the Comp Panel, the color values flash for a split second and go away. If I press Opt+1 (2, 3, and 4) the Info Panel displays the color for that one pixel but the values go blank as soon as I move my mouse. This happens in the Comp Panel mostly. If I open a Footage or Layer Panel, sometimes the values show, sometimes not. Never had this issue in previous versions.

Similar Messages

Two Custom File Info Panel Issues

When I add a second custom file info panel that has a different name (panel, .xml, and folder), the panel name that appears is the same as the first. What is causing this?

Hi,
here is how it works:
If you open the properties.xml you will find a zString key for every label:
i.e. label="$$$/Custom/Schema/Label=Custom Properties" (which is the panel name).
Depending on the language of the application it will load the values from the zstring files. If there are no files it will use the value of the properties.xml.
So if you want to change any label it is not enough to change the value in the properties.xml or the folder name. Is you leave the key as it is it will load the value based on the key. So you have to change the key and value in both the properties.xml and the Generic_en_US.dat and all other language files you would like to support.
example:
properties.xml:
label="$$$/Custom/Schema/Label2=Custom Properties 2"
*.dat:
"$$$/Custom/Panel/Label2=Generic Panel 2"
Or you remove the Keys completly from the properties.xml, but then multilanguage is not supported.
Hope this helps,
Samy
P.S. You can test different languages by changing for example Bridge to a different language (in the settings) and restart it. If you then open FileInfo it will load the correct *.dat files based on the language. You can add more *.dat files for more languages for you panel if you like.

Custom File Info Panel CS2- CS4

I have a Custom File Info Panel that has been created in Adobe Photoshop CS2 and works in CS3. I am having trouble figuring out how to get it to work in CS4. Is there a way to port the Custom File Info Panel into CS4 without entirely recreating it?
I am seeing references to FileInfo SDK and creating a new Flex UI but I can't seem to find a definitive method on this pre-CS4 File Info Panel to the new UI - and I am in unfamiliar territory.
Any assistance or points in the proper direction would be most helpful.
UPDATE: Answering at least some of my own questions, I have followed the procedure here:
http://blogs.adobe.com/gunar/2008/11/customizing_metadata_ui_in_cs4.html
I am still having some trouble with a couple of the unique properties but I expect that they will be typos... I hope...
Any good reference information is still welcome.

Thank you for suggesting the PS Scripting forum but I think the next stop might be the XMP SDK Forum as there are a few similar questions there such as http://forums.adobe.com/thread/540397. But before I go impolitely cross-posting...
I've had some success and it appears that my custom file info metadata edited and saved in CS2 is now visible in CS4 and the reverse is also true - metadata edited and saved in CS4 is visible in CS2. This was built using the Generic Panel from the SDK according to the instructions shown at the link in my original post.
The only problem is that the external application that relies on the custom metadata doesn't see the CS4 version of the metadata. I suspect that this is just some general namespace issue. Perhaps if an XMP expert would be willing to comment on the conversion of the Custom Info Panel based on the following single portion of the metadata to see if I am doing it correctly - I would very much appreciate it.
In the CS2 Custom Info Panel XML I have this field:
<panel title="$$$/CustomPanels/XYZ/PanelName=XYZCorp Graphics MetaData" version="1" type="custom_panel">
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/CustomPanels/XYZ/fullName=Full Name/Title of Graphic', font: font_big_right, vertical: align_center);
cat_container_edit_text(xmp_ns_prefix: 'xyzcorp', xmp_namespace: 'xyzcorp', xmp_path: 'FullName', container_type: seq_struct, horizontal: align_fill);
mru_popup(xmp_ns_prefix: 'twcable', xmp_path: 'FullName', no_check: true, vertical: align_top, container_type: seq_struct, mru_append: true);

</panel>
In my CS4 properties.xml the corresponding field:
<xmp_definitions xmlns:ui="http://ns.adobe.com/xmp/fileinfo/ui/">
<xmp_schema prefix="custom" namespace="xyzcorp" label="$$$/Custom/Schema/Label=XYZCorp Graphics MetaData" description="$$$/Custom/Schema/Description=CS4 Version of XYZCorp MetaData Custom Panel.">

<xmp_property name="FullName" category="external" label="$$$/Custom/Property/FullName_Label=Full Name/Title of Graphic:" type="seq" element_type="text"/>

<ui:separator/>
</xmp_schema>
</xmp_definitions>
It seems that the following CS2 => CS4 translations should be true:
"xmp_namespace" => xmp_schema namespace property (in this case "xyzcorp")
"xmp_path" => xmp_property name property (for this one property, "FullName")
is there another translation that I am missing? I am betting it has something to do with the CS2 "xmp_ns_prefix" but I am not entirely sure how to map this. Also perhaps something in manifest.xml (though it didn't seem like it)?
Many thank you's to anyone that can offer words of wisdom.
j

Custom File Info Panel: Bridge Locks Up (trials, tribulations, woes)

o/ all!
So I've spent the better part of this morning trying (for what I think is the fifth time this year) to get a custom file info panel installed properly. I've managed to successfully install a generic panel with most of the properties that I'd like in the panel proper, however, I'm having no end of trouble publishing and installing the panels and having them display properly in Bridge CC (64-bit).
I've followed the instructions provided in the Programmer's Guide to the letter (yes, including the trust files), and I'm still having issues.
-- System Information --
OS: Windows 7 64-bit
Flash Builder 4.7 (64-bit)
Adobe Bridge CC (64-bit)
Right now, all I'm trying to do is:
Create the flash builder project for an XMP File Info Panel
Publish the file info panel
Confirm the file info panel was installed correctly in Adobe Bridge CC.
The process:
1. I create the new project in Flash Builder (I've attempted using the 4.6.0 and 3.6A flex SDKs).
Now, at this point, I'm simply attempting to confirm that everything is hunky-dory with the installation process before I start converting my generic panel into a flash/flex panel; so I'm not modifying any of the files that the wizard created.
2. Right-click the root project folder in the leftmost pane in Flash Builder, select XMP>Publish.
3. Locate the published panel's output directory that Flash Builder published to
4. Copy/paste the published panel's root directory to the following directories:
C:\Users\Erik\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\panels\
C:\Users\Erik\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\custom\
C:\Program Files (x86)\Common Files\Adobe\XMP\Custom File Info Panels\4.0\panels\
C:\Program Files (x86)\Common Files\Adobe\XMP\Custom File Info Panels\4.0\custom\
I put the panel definition in all of these folders as per various 'fixes' to what I think my issue is that I've discovered while google-troubleshooting.
5. Create a trust file in FlashPlayerTrust folder with the name testPanel36A.cfg (contents listed below):
C:\Users\Erik\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\panels\testPanel36a\bin\testPanel36a.swf
C:\Users\Erik\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\custom\testPanel36a\bin\testPanel36a.swf
C:\Program Files (x86)\Common Files\Adobe\XMP\Custom File Info Panels\4.0\panels\testPanel36a\bin\testPanel36a.swf
C:\Program Files (x86)\Common Files\Adobe\XMP\Custom File Info Panels\4.0\custom\testPanel36a\bin\testPanel36a.swf
As far as I know, I can put multiple paths in these .cfg files, but I'm not-at-all confident that this is, in fact, the case.
After all this, I fire up bridge, right click an image file, and select FileInfo. The dialog displays fine, and the panel tab appears on the right. Clicking on the panel reveals nothing but a gray area with no content, and Bridge locks up entirely. I can't cancel out of the dialog, and end up having to end the process from Task Manager.
My gut tells me that I'm doing something wrong with the trust files, as this seems like the issue that most closely resembles what I'm encountering. Secondarily, It may be the flex SDKs -- I only have the 4.6.0 and the 3.6A SDKs, and the link in the Flash Builder dialog takes me to the sourceforge page for Adobe, and from there, I cannot locate any additional older SDKs to try this with (I've seen posts around saying that people got their panels to work with 3.0, or 3.5).
Anyone have ANY insight on this? Seriously at my wits end -- I've tried everything but nothing seems to work . Many thanks,
.e

Hi The_Mumm,
     You need to correct content fo the .cfg file (hope your .cfg file is at correct directory i.e. C:\Documents and Settings\<user name>\AppData\Roaming\Macromedia\Flash Player\#Security\FlashPlayerTrust). Yes, I agree that you have followed the documentation and put the path upto .swf file.
    Could you please modify the content of the trust file, with the below content (you path have been modified)
C:\Users\Erik\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\panels\testPanel36a\bin\
C:\Users\Erik\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\custom\testPanel36a\bin\
C:\Program Files (x86)\Common Files\Adobe\XMP\Custom File Info Panels\4.0\panels\testPanel36a\bin\
C:\Program Files (x86)\Common Files\Adobe\XMP\Custom File Info Panels\4.0\custom\testPanel36a\bin\
Hope everything will work now. If it doesn't work, please put only one path in trust file e.g. "C:\Users\Erik\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\panels" and put the publish panel in this folder.
One more precaution, don't copy, if required move the custom panel from one place to other.
Please let me know if you still faces any issue. Enjoy you new year.
For your reference, I am following the following steps and everything is working fine
1. Open the Fb7,
2. file->new->project
3. in the new project wizards, select "xmp->custom panel wizard"
4. xmp->publish custom panel
5. Open the .cfg file and added the path (C:\Users\<user name>\appdata\Roaming\Adobe\XMP\Custom File Info Panels\4.0\panels) where my panel has got published.
6. Ran Bridge CC, panel is there and working fine.
One more variations I did is, moved custom panel from C:\Users\<user name>\appdata\Roaming\Adobe\XMP\Custom File Info Panels\4.0\panels to C:\Program Files\Adobe\Adobe Bridge CC (64 Bit)\Custom File Info Panels\4.0\panels (the location of the custom file info panel inside bridge).
      For you doubts I tried with flex SDK 3.3A and 3.6a both worked fine. As in forum you have written that you don't have any other sdk. If you like please go on the following links for older SDKs "http://sourceforge.net/adobe/flexsdk/wiki/Download%20Flex%203/"
-Sunil

XMPComboBox and XMPDateField probems in File Info Panel

Hi,
I have used Flash Builder 4 with the XMP FileInfo 4.4.2 SDK to build the example Custom File Info Panels.
None of the examples worked using the Flex 3.5 or 4.0 SDKs (blank panels in photoshop).
The example panels build and show in CS4 when I configure Flash Builder to use the Flex 3.0.2 SDK(last stable build of 3.0) .
The panels create and show usable XMP metadata but dropdowns combo boxes don't work and neither does the popup calendar on the date field.
The panel I have to build will require functioning Comboboxes and Popup calendars.
Can you let me know if there is anything I can do to resolve this issue?
I would switch to using CS5 but my company is using over 2000 CS4 licenses.
Thanks,
Paul.

Hi Stephan,
1. I'm on Windows 7.
2. I installed the precompiled examples like this:
copy \XMP-FileInfo-SDK-4.4.2\samples\panels\BasicControlSamplePanel directory to :
C:\Program Files (x86)\Common Files\Adobe\XMP\Custom File Info Panels\2.0\panels\BasicControlSamplePanel
The ComboBox dropdown and DateField calendar pop-up works fine in the CS4 photoshop fileinfo panel.
Here's the problem:
I also built the panel in Flash Builder 4 by importing this directory
\XMP-FileInfo-SDK-4.4.2\samples\panels-src\BasicControlSamplePanel
I downloaded 3.0.2 Flex SDK , configured FB4 to use it and chose "Use a specific SDK:" 3.0.2 in the Flex Compiler section.
I changed the runnable Flex applications to use src\examples\BasicControlSamplePanel.mxml
I left the rest of the project properties at default.
I ran an Export release build.
I copied the \target directory to :
C:\Program Files (x86)\Common Files\Adobe\XMP\Custom File Info Panels\2.0\panels\BasicControlSamplePanel
I copied the \bin-release\BasicControlSamplePanel.swf file to :
C:\Program Files (x86)\Common Files\Adobe\XMP\Custom File Info Panels\2.0\panels\BasicControlSamplePanel\bin
In this case ComboBox dropdown and DateField calendar pop-up DON'T work in the CS4 photoshop fileinfo panel.
I have built all the other samples similarly in the SDK and their dropdowns and comboboxes don't work either!
I couldn't find a FileInfoFoundation.swf file but I did find a FileInfoFoundation.swc file - where would i get a FileInfoFoundation.swf file?
I wasn't sure what you meant , so I copied FileInfoFoundation.swc to :
C:\Program Files (x86)\Common Files\Adobe\XMP\Custom File Info Panels\2.0\panels\BasicControlSamplePanel\bin
It didn't make a difference!
Is there something I'm missing or something else I need to do?
Thanks for your help on this.
Paul.

BUG: Info panel displays incorrect Hue values

Recently, I've been doing a lot of work with color in Fireworks and came across the following bug, which appears to be a longstanding issue within the application. Rather than keeping it to myself, I figured I'd post it here in addition to submitting a bug report with Adobe. So here it is...
Hue values displayed within the Info panel (in HSB mode) do not consistently match the values displayed in the Color Mixer panel—including basic colors such as pure Yellow, Cyan, and Magenta. The values are 1 degree off—most often below the Color Mixer value, but sometimes above (as with Magenta). This holds true whether using with the Eyedropper tool or the Color Picker swatches eyedropper, and whether sampling from the canvas or from swatches.
For example, the following inconsistencies were observed when sampling the centermost horizontal strip within CS6's default Color Cubes swatches picker. Note that over 50% of these colors are affected by the issue.
The Color Mixer seems to display the correct values, while the Info panel's values appear to be incorrect. Note that this issue affects the HSB mode only; the RGB and Hex values are consistent between both panels.
This bug has been observed in Fireworks CS6, Fireworks CS5.1 and Fireworks 8 on Mac OS 10.6.8 (Snow Leopard).
Here's the bug report submitted for this issue:
Product name: Fireworks
Product Version: 12.0.0.236
Product Language: English
Your operating system: Mac OS 10.6.8 (Intel-based)
******BUG******
Concise problem statement: The Info panel displays incorrect Hue values for many colors—including pure Yellow, Cyan, and Magenta. The Hue values are usually 1 degree below the value displayed in the Color Mixer panel (e.g., 59 instead of 60 for Yellow) but sometimes 1 degree above (e.g., 301 instead of 300 for Magenta). This is true whether using the Eyedropper tool or the Color Picker swatches eyedropper, and whether sampling from the canvas or from swatches.
Steps to reproduce bug:
In an open Fireworks document, open the Info, Color Mixer, and Swatches panels. Within the Color Mixer and Info panels, set the color mode to HSB.
Draw a Rectangle and set its fill to Yellow (#FFFF00) using the Color Picker.
Observe the Hue values displayed in the Color Mixer and Info panels.
Select the Eyedropper (I) tool, and sample the rectangle's fill color. Again, observe the Hue values displayed in both the Color Mixer and Info panels.
Results: In both steps 3 and 4, the Hue value for pure Yellow (#ffff00) appears as 60 degrees in the Color Mixer panel but 59 degrees in the Info panel.
Expected results: The Hue for pure Yellow (#ffff00) should appear as 60 degrees in both panels.
Note that this issue affects the Info panel's HSB mode only; the RGB and Hex values are consistent between panels. Also note that this bug affects over 50% of the "pure" hues within CS6's Color Cubes swatches palette. For more info, see the following forum post:
http://forums.adobe.com/thread/1083391
This bug has been observed in Fireworks CS6, CS5.1 and FW8 on Mac OS 10.6.8 (Snow Leopard).

I haven't done anything other than add my footage to the timeline. I have 2 layers (1 targa seq and 1 png seq). As I move my mouse from the Timeline to the Comp Panel, the color values flash for a split second and go away. If I press Opt+1 (2, 3, and 4) the Info Panel displays the color for that one pixel but the values go blank as soon as I move my mouse. This happens in the Comp Panel mostly. If I open a Footage or Layer Panel, sometimes the values show, sometimes not. Never had this issue in previous versions.

Custom Info Panel as Bridge MetaData Panel

Hello,
I have built a Custom XMP InfoPanel that shows up in CS6 Bridge just fine! But for ease of data entry we want it to show up in the Bridge MetaData panel. How is this done with the latest best practices?
I have looked everywhere found a number of ways, but ALL are out dated! The XMP FileInfo SDK doesnt cover this.
Thank you
Dean Krueger

Hi Science_DC,
    You are missing the zstring in your label or description and the same issue is with properties too. For testing i changed only two properties but you need to do the smae for others too. I tested after using the ZString and it's working fine in Bridge too. Please find the original and modfied code (only for two properties)
1. Your original properties.xml is
<xmp_schema prefix="custom" namespace="http://my.custom.namespace/" label="<Your label>" description="<Your Panel Description>">
        
        <xmp_property name="Text" category="external" label="<Property Name>" type="text"/>
        <xmp_property name="Text2" category="external" label="<Property Name>" type="text"/>
</xmp_schema>
Insert the ZString like below (inserted text are in bold)
<xmp_schema prefix="custom" namespace="http://my.custom.namespace/" label="$$$/Custom/Panel/Label=<Your label>" description="$$$/Custom/Panel/Description=<Your Panel Description>">
        
        <xmp_property name="Text" category="external" label="$$$/Custom/Panel/Property1 Name=<Property1 Name>" type="text"/>
        <xmp_property name="Text2" category="external" label="$$$/Custom/Panel/Property2 Name=<Property2 Name>" type="text"/>
</xmp_schema>
2. Put that propery file in Custom File Info Panels/4.0/panels (at the same place where DCIM.xml and mobile.xml is)
Following is the screen shot which I got after ZString insertion (CS6 Bridge)
If it doesn't work, could we do remote desktop?
-Sunil

File info Panel doesn't show up in CS6 apps

Hi all,
I have compiled a File Info Panel with EB2. It opens fine in CS5.5 apps but it's not accessible with CS6.
I can't see any settings in EB2 to have both versions supported. I also tweaked the manifest and get the ZXP recompiled but then althought the panel does appear, the content isn't built.
Any hint on what's happening ?
Best,
Loic

Hi Loic,
Do you know what directory you are installing the panel to? Is it /Users/<username>/Library/Application Support/Adobe/XMP/Custom File Info Panels/3.0/panels/
Can you try placing the panel inside of /Users/<username>/Library/Application Support/Adobe/XMP/Custom File Info Panels/4.0/panels/ instead. If your panel does not display when you open the FileInfo dialog on your development machine then you may need to adjust the flash player trust file so it is pointing at the 4.0 directory; /Users/<username>/Library/Preferences/Macromedia/Flash Player/#Security/FlashPlayerTrust
In the MXI file update the paths so it deploys to the 4.0 directory.
I will forward this issue onto the Extension Builder team as it seems supporting FileInfo panels between suite versions is not currently available.
Kind regards,
Lea

Info panel won't open

Sometimes when I open iPhoto, the sliding panel on the side of the library is pulled to the far left, so the info panel, slideshows', albums, etc, are not visible.
When I click on the little marking [don't know what its called] that slides the window back, it has no effect...... sometimes for quite awhile and then......again, for no apparent reason, it works and I'm able to slide the library window to the right so I can access the calendar, info panel etc....
Does anyone know why it does this, or how to fix it when it does ?
Thanks

move your mouse to the far left and when it turns into a + sign click and drag to the right
or renew the iPhoto preference file - A good general step for strange issues is to renew the iPhoto preference file - quit iPhoto and go to "your user name" ==> library ==> preferences ==> com.apple.iPhoto.plist and trash it - launch iPhoto which creates a fresh new default preference file and reset any personal preferences you have changed and if you have moved the iPhoto library repoint to it. This may help
LN

Info panel not displaying eps info

I cannot get the ppi information to display in the info panel. Is this some new spangly feature of InDesign, or a bug?

Clarification of what is claimed, and why we are perpetuating this conversation.
John, that's jut nit picking at what I said.
Sorry, I tried to make it clear, it's a nit but I think it is a very important one. Please feel free to disagree. But when we're talking about whether a file format that's important to people is doing to be supported, or is going to go away, it's very important to be clear about the public statements that have been made. Similarly, I do get bothered when EPS is described as "archaic" or "obsolete." It fills needs that are not filled by PDF or AI files, and while it is certainly older than PDF, it is of peer age to TIFF and JPEG. It is certainly less frequently used, and in many applications there are better choices (like PDF). But not in all.
The issue of "double standards."
John, nor do you really say why you think EPS is preferred. Double standards here.
I'm sorry, but please reread my post. I do not say that "EPS is preferred." I talk about several things it can and cannot do, and explain why, for instance, it and PDF show some of the same deficiencies in InDesign's Info panel. I tell you some reasons that I like it. But I do not in fact believe that it is a "better" format most of the time, and make no such claim. It is unfair to ask me to substantiate claims I did not make. I tried to be quite careful on this one.
Yes, generally PDFs are better. But.
You have produced quite a link storm there, but I'm afraid they don't do a terribly clear job of explaining why these other formats are better than EPS, and for exactly which applications. If your point is to say that in general, one should not prefer EPS over PDF, then that's fine. I think it is a true statement.
What bothers me about the statements in this thread (and this forum in general frequently echoed on this forum) is that it is wrong to use EPS; that EPS is obsolete; that Adobe InDesign will drop support for EPS; that EPS is archaic. That's simply not the case. It might be the wrong format for bigdrunk (it probably is; but we don't really know what he is doing). It is not the wrong format for everyone.
Addressing the external links/references
But we should be clear on what we're talking about. Your initial link, to Real World Illustrator's What's in a file? does a great job of describing the output formats from Illustrator. It doesn't really make a recommendation, other than to note that PDF supports some features that EPS does not. Transparency being the key point, and we've mentioned that only four times before your post. I'm not sure if that's the "plain as day" or not.
Adobe's David Evans' psvspdf post similarly discusses both formats, and suggests that EPS is a replacement for PDF -- which it is. But that only gets you so far. It doesn't address the fact that PDF files can have downsides compared to EPS files (many articulated above in the thread), but really just says that PDF can do most of the things that EPS can do. That's certainly true. After all, you can put EPS files inside PDF files! But that doesn't tell you that you're better off writing to a PDF file in any particular case. To pick a few examples from above, some apps can only read EPS files and can't read PDF files. And others can generate EPS files much more easily than they can generate PDF files.
I am rather apalled that you would cite eHow. They are rather notorious for giving bad advice that is not vetted by experts. In this case, though, the eHow post merely answers the question, "If an EPS file won't work, what are the alternatives?" It seems to do so correctly, but its not relevant to this discussion.
Craig Kirkwood's Pixel Therapy link is more general advice, for "How should I save my Illustrator work?" And again, none of us here who are speaking up for EPS are saying that it is the preferred file for Illustrator work (though I did point out that Illustrator can produce smaller EPSs than PDFs, which is bizarre).
PDF-in-AI or AI-in-PDF?
(although I disagree about saving as PDF from Illustrator with editing capabilities, best to save as ai with PDF)
Why do you think so? In general, they should be equivalent -- in both cases a PDF file is available to PDF-reading applications, and in both cases (and in Illustrator EPS, by the way), Illustrator private data is preserved for full Illustrator editing capability. I would say that distributing .PDF files is a better choice, because if a non-expert person receives a .ai attachment in their email, they are more likely to be confused about how to view, print or render it than they would be if they receive a .pdf file. That may not sound like the most compelling reason, but I can't think of one that is more compelling.
No flat recommendation of EPS over PDF.
I quite literally CANNOT find one source that recommends EPS over AI or PDF???
I wonder why that is?
To be honest, I think it is because there are very few experts on these file formats. You need to really understand the low-level file format to be qualified to offer an opinion on the merits of the file format by itself. And the merits of the file format aren't really the point most of the time -- what matters is the applications that you use, and how they handle it. Does a given application produce better PDF files or better EPS files. Does another application read EPS files better than it reads PDF files? Are there apps that read or write one but not the other? Is there a savings in file structure, in maintenance, in cost, in aggravation.
Most of the people who write about these things are aware of the ramifications and the practical effects of the choices, but not the low-level details.
Most of the time the low-level details do not matter. But they do indeed matter to some of us, and it is those of us who have spoken up in this thread.
In favor of EPS, but in a limited way.
Why EPS is sometimes better.
Can you explain why you think EPS is better than ai or PDF? Can you point me to any online sources, or books?
As we have enumerated in this thread (and the other recent one, I guess), EPS has the following potential advantages over PDF; they may not be important to you, but they are sometimes important to some of us in some cases:
1. It can be easily authored by humans and tools without requiring complex tools to convert into intermediate formats (e.g. Acrobat Distiller; pstopdf or GNU Ghostscript; expensive libraries to produce PDF output);
2. If appropriately written, it can produce human-readable ASCII output that can be understood by someone familiar with EPS. For programatically generated output, seeing that the code says "Draw a circle at coordinates (1 inch, 1 inch)" can be extremely valuable. In such an EPS file, that might be "1 inch 1 inch drawcircle."
3. Bitmap binary data can be more efficiently JPEG encoded in EPS than in PDF. (I was not aware of this, and do not know it to be the case. But Uwe mentions it.)
4. Gernot's point regarding direct CMYK specifications. I'm honestly not sure what it is, so I won't try to explain it.
5. Some apps output cleaner EPS files than they do PDF files. Apparently Illustrator is one such app. Which is bizarre.
6. Some applications/clients/specifications require EPS, such as the CUMULUS database.
As for AI, well, as we've already said above AI and PDF are essentially equivalent, as both can contain PDF images and Illustrator private data. But EPS is certainly better than Illustrator private data because it is an open, well-documented standard. Anyone with enough time on their hands can interpret an EPS file acording to a public, published spec that's been around for years. There are free and commericial software PostScript renderers, and there are an abundance of PostScript printers. None of those things are true for AI.
The rest.
What's left? I think that's really about it. You've spent quite a bit of time arguing against a position I do not think anyone was adopting.

File Info panels in Lightroom.

Hello, everybody.
My workflow involves the use of Photoshop, Bridge and more recently I decided to make Lightroom part of it also. As described in Martin Evening's "The Adobe Photoshop Lightroom 2 Book" I am trying to use Bridge as a front end for Lightroom and think that both applications really complement each other well.
Now, to my questions:
1. I am trying to find the File Info panels in Lightroom that can also be accessed in Photoshop and Bridge. I must have missed the obvious but I haven't been able to find it. Could you point me in the right direction ?
2. Where is the keyword catalog for Lightroom located ? What is the proper syntax for this file ? Is there an application I can use that will allow me to create my own keyword catalog that can then be imported into Lightroom ? Last but not least, can Lightroom have more than one catalog installed ? What about Bridge ? Can it also have more than one keyword catalog installed ?
Thanks,
Joe

Those panels are specific to Bridge, Photoshop and other Adobe suite apps. Sadly, they don't exist in LR. Instead, use the Metadata panel.
LR's keywords are stored inside the LR catalogue - there is no "keyword catalog for Lightroom" concept. You can import a list of keywords using the Metadata > Import Keywords command. This list will be a txt file which you can prepare in any text editor or in Excel. To see the format, add a few keywords in Lightroom, and create a txt file using the Metadata > Export Keywords command. Then just edit this file, or copy its format - eg indenting child keywords.
Fr now, if you are asking questions like these, I would recommend sticking to one tool, a single Lightroom catalogue, for entering your metadata. Until you find your feet, using more than one tool will only make work for yourself and will result in inconsistencies. Also, treat yourself to a copy of Peter Krogh's DAM Book (his forum is good for metadata workflow issues).
John

Which one is right? The colour picker or the info panel?

Try this one out at home kids:
Set your colour picker to Greyscale and dial 25% K into your foreground colour swatch.
Now, in a new, RGB document, fill that document with your foreground colour.
Now open the Info palette, set one of your readouts to "Greyscale" and enjoy seeing it read 31% K.
Uh.
WTF?
My RGB readout reads 192 across all channels, which is correct: 192 / 256 = 75% (additive) = 25% (subtractive)
This probably has something to do with colour management, but could someone A) explain to me what is happening, and B) tell me how to set it so I can get mathematically predictable results?

D Fosse wrote:
I'm not trying to argue...well, I am - but if you could explain precisely what you're after I'm sure it's doable.
Dag, did you go through the exact sequence he put up in the first post?
The issue is that we seem to be able to set the absolute numbers for RGB in the COLOR panel (made visible through the Window - Color) menu via choosing Grayscale and a %K value - in this case 25% sets color (192, 192, 192). It sets these values no matter what profile the document is using.
When that color is used on any old document, the profile is involved with reading back the number in the %K portion of the info panel.
No profile is involved with setting the number (because this operation doesn't involve a document), a profile IS involved with reading the number from a document. That difference is at the root of the issue Tom is sensing, I think.
My comment about Photoshop being developed on a Mac... Note that with a profile carrying gamma 1.8, Photoshop DOES make the numbers match., probably owing to a hard-coded gamma correction in the logic of the info panel. It might be more reasonable for it to just use the gamma derived from the profile, or just do a conversion to linear space first, but then that would change the way Photoshop works, and Adobe appears to have a policy of "keep it very consistent with past releases, so everything still works".
-Noel

After Effects and Rotoscoping causes fps loss in info panel

Hello,
I am pretty new to after effects, so please take it easy on me if this is an easily fixed issue or if I am doing something wrong. Here is my whole process.
I have a canon xl2, shooting in 24p with 2:3 selected. I then import the video from the camera to premiere using capture. This was filmed at 16:9.
In PP I open a new project, I use DV - 24p Widescreen 48khz. I have the time code set to auto detect in capture.
I then import the captured video to after effects. I am trying to get better at rotoscope brush, so this is where the problem is.
I import the file, drag the source to the new composition icon, then double click the layer in the composition. I select rotobrush and brush the object.
I then select play, which will go thru and play the file, adjusting the rotobrush. As I view the file, my info panel is up and it begins by showing 23.976 (realtime). The preview panel is showing 23.98 fps.
After a few seconds, the rotoscoping fails and the info panel shows my actual fps vs the file fps. SO in red it shows something like 7.005/23.976 NOT realtime.
I've tried to do some research on this, and I am not sure if everything is set up right. I have read that its best to work on noninterlaced video in AE, i believe it is seperating. In interpret footage it is showing under fields and pulldowns area: lower field first and then it is removing pulldown with WWSSW. Showing a effective framerate of 23.976. Under frame rate area i have selected [conform to frame rate] and 29.97 is in the window. Under pixel aspect i have widescreen 1.21.
I know this is a huge wall of text, but I'd rather swamp you with info then not have enough. Any ideas on what I am doing wrong? Why the fps drops out so much on the rotoscope? Also note, I am only losing fps after pressing play to have rotoscope find the edges itself.
Thank you for any help on this matter.
further info:
Running window 7 pro - 64 bit, adobe CS5 production premium. At the moment its the trial version - get my copy in the mail tommorrow.
PC is i7 920 oc'd to 3.6, 6 gigs ram, 7200 rpm HD with 64Mb cache, gtx480 with 1500Mb Vram. Using the latest Nvidia drivers.
I believe I am using OpenGL for rendering, but not positive.

Ok, awesome. Thanks a ton for taking the time to explain it to me and make sure that I understand the proper way to reference it.
With all this considered, is there any reason why someone would do the traditional rotoscoping vs using the rotobrush to create a matte?
To me it seems like the roto brush pretty much replaces traditional rotoscoping. If thats the case, wouldn't it almost be considered a new rotoscoping method.
Like in the past, people used to dig holes with shovels and by hand. Excavating holes this way was hard and took alot of time.
Over the years, technology made it possible to use a backhoe to dig holes, making it super easy. Both methods are excavating, one is just using an easier method.
I guess thats where my confusion came in, I guess the way I look at it, due to never having done the traditional rotoscoping method, I just considered it the same thing.
Anyway, I hope I dont look like a giant *** with my posts. Cuz anyone willing to take time outta there day to help someone else in a courteous manner deserves all the praise I can give.
Thanks again.

Finder - "Get Info" - "More Info" panel has NO information any more!

Hello all,
Can you help a slider out? My new MacBook Pro has a problem with the Finder. When I use the Finder, File, Get Info (or Command I), to get info about a file, in particular, a graphic file, I used to see stuff in the "More Info" panel. I use the image size information (e.g., 512 x254 pixels and the actual memory size) to quickly keep track of graphics for my web pages.
Well, for ALL file types now, I get NO "More Info" information in the panel. All the other panels, "General", Name & Extension", "Open with", "Preview" and "Ownership & Permissions" work fine.
I fixed disk permissions via the Install DVD and deleted the com.apple.finder.plist and neither of these have helped resurrect my "More Info" information.
I am running 10.4.10 and this is only on my machine. On the other 2 in our household, the panel works as it always has.
HELP, I miss my "More Info" info!
TIA,
Dave
[email protected]

I am also encountering the same issue...in addition, I'm having trouble installing Google Sketchup Pro 6, I believe there may be some sort of correlation between the two?
Any help?
-j

How to make my old file info panel from photoshop work in xmp

Help. Not a photoshop guy but rather a genealogist. Many years ago downloaded a custom file info panel for photoshop which I used to enter meta text about the family photos I scanned. Currently using adobe creative cloud but cant figure out how to use panel or see most of my metatext last few version. Below is information about the panel. All I really want to do is install my panel and get back to genealogy. I apologize but not sure I need to understand the basics of photoshop..
john weis
[email protected]
This is the authors description of the panel:
Genealogy Photo (Private Collection) Custom File Info Panel 1.0 for Photoshop. 11 FEB 2007
Developed by Ron Reiger [email protected]
Please contact me to suggest improvements.
1. BASIS FOR THIS CUSTOM FILE INFO PANEL
2. DESCRIPTION OF EACH PROPERTY NAME
3. WHERE EACH PROPERTY NAME MAPS & OTHER NOTES
4. WHERE TO INSTALL THE CUSTOM FILE INFO PANEL
1. BASIS FOR THIS CUSTOM FILE INFO PANEL
The Custom File Info Panel is used to capture metadata about a genealogy/family history photo that is privately held (that is, the photo is not in the possession of a library). The metadata property names on the File Info Panel are based on my interpretation of the recommended primary citation for a photograph (private possession) (annotated, with provenance) as described on page 95 of Elizabeth Shown Mill's "Evidence! Citation & Analysis for the Family Historian" and on my interpretation of recommended primary citation for an Electronic File (Image from Private Files - Annotated), Mills, "Citation!", page 81. I added a few more property names for location and date the photo was taken and keywords (to ID people by number rather than by name), the name of the person who provided the description, a surety for their description, and an informal description. Each field is discussed below.
2. DESCRIPTION OF EACH PROPERTY NAME
Date Scanned: This is the date the photo was scanned. Date is populated by Photoshop and is not editable.
Provider: The owner of the photo as of the date it was scanned. A researcher in a future generations will know who had the photo at a particular point in time.
Provenance: Describe as best you can how the photo got from the person in the photo to the Provider.
Description Provided By: List the person who identified the people and location in the image.
Description Surety: (This is an open text field. You can use any surety rating system you want.) Describe or rate the quality of the Description of the image's people and location. Note any uncertainties regarding any particular people in the photo.
Complete Subject Description: List the full name of each individual in the image, in order. You may want to list the location and date of the image even though there are separate property names for that data.
Informal Subject Description: An optional non-genealogical description of the image, perhaps for using the photo outside of genealogy. Example Informal Subject Description: "Grandpa as a young man."
Media Description: Describe the paper photo you scanned. Dimensions, border, frame, damage, etc. Your ancestors will have an easier time finding the paper photo later if you describe it well!
Annotations: Copy any annotations on the front or back of the photo and frame. Transcribe any photographer embossing/imprint; this is a clue for dating/locating photos.
Special Editing/Alterations: Describe any restoration you performed on the digital image. Did you correct for the lateral reverse of a tintype or daguerreotype?
City/County: List the City/County where the image was taken.
State: List the State where the image was taken.
Country: List the County where the image was taken.
Photo Date: List the date the image was taken.
Keywords: This is the standard keyword entry. Commas or semicolons can be used to separate keywords. I type the TMG ID number of each person in the photo here so I can search for all photos of the person without typing their name.
3. WHERE EACH PROPERTY NAME MAPS & OTHER NOTES
I have not created a working namespace URI or rdf ala http://purl.org/dc/elements/1.1/ for this panel. I have not created localization dictionary files for this panel. Data entered into the panel will appear in Adobe Bridge. As you can see below I re-used lots of pre-existing property names and dumped all my new property names into the photoshop namespace. I don't know if this approach has drawbacks.
Date Scanned:                xmp_path: 'CreateDate'   Pre-existing property name
Provider:    xmp_namespace: photoshop, xmp_path: 'Credit'    Pre-existing property name
Provenance:    xmp_namespace: photoshop, xmp_path: 'Provenance'
Description Provided By: xmp_namespace: photoshop, xmp_path: 'DescriptionProvidedBy' Pre-existing property name
Description Surety:   xmp_namespace: photoshop, xmp_path: 'DescriptionSurety'
Complete Subject Description:   xmp_namespace: photoshop, xmp_path: 'Description'   Pre-existing property name
Informal Subject Description: xmp_namespace: photoshop, xmp_path: 'Caption'   Pre-existing property name
Media Description:   xmp_namespace: photoshop, xmp_path: 'MediaDescription'
Annotations:     xmp_namespace: photoshop, xmp_path: 'Annotations'
Special Editing/Alterations: xmp_namespace: photoshop, xmp_path: 'SpecialEditing'
City/County:    xmp_namespace: photoshop, xmp_path: 'City'    Pre-existing property name
State:     xmp_namespace: photoshop, xmp_path: 'State'    Pre-existing property name
Country:     xmp_namespace: photoshop, xmp_path: 'Country'   Pre-existing property name
Photo Date:    xmp_namespace: photoshop, xmp_path: 'DateCreated'   Pre-existing property name
Keywords:               xmp_path: 'Keywords'   Pre-existing property name
4. WHERE TO INSTALL THE CUSTOM FILE INFO PANEL
I have tested this panel with Photoshop CS2 and Adobe Bridge CS2 only. It may not work on earlier versions. FWIW a malformed Custom File Info Panel will fail to load in File Info; it won't crash Photoshop.
The following was taken from "XMP Custom Panels," Adobe, Oct 2003.
Each time an Adobe application opens the File Info dialog, it scans all the files in these directories and appends them to the file list. If more than one of the description files has
the same panel name, the one found in the last file to be loaded is added, and others are ignored.
Changes to the contents of the directories do not require you to reload an application; changes are automatically reflected in the dialog the next time it is opened.
The panel description and localization dictionary files must reside in the following locations for use with Adobe Creative Suite applications:
Mac OS X
{Root Volume}/Library/Application Support/Adobe/XMP/Custom File Info Panels
{Home Directory}/Library/Application/Adobe/XMP/Custom File Info Panels
Windows
\Program Files\Common Files\Adobe\XMP\Custom File Info Panels
\Documents and Settings\<user>\Application Data\Adobe\XMP\Custom File Info Panels
The panel description and localization dictionary files must reside in the following locations for use with Adobe Acrobat 7.0 or 6.0:
Mac OS X
{Root Volume}/Library/Application Support/Adobe/Custom File Info Panels
{Home Directory}/Library/Preferences/Adobe/Custom File Info Panels
Windows
\Program Files\Common Files\Adobe\\Custom File Info Panels
\Documents and Settings\<user>\Application Data\Adobe\Custom File Info Panels
I actually do not understand how to write a panel but here is the actual panel:
<?xml version="1.0">
<!DOCTYPE panel SYSTEM "http://ns.adobe.com/custompanels/1.0">
<panel title="$$$/CustomPanels/Acro/PanelName=Gen Photo (Private Collection)" version="1" type="custom_panel">
group(placement: place_column, spacing: gLargeSpace, horizontal: align_fill, vertical: align_top)
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/AWS/FileInfoLib/Panels/Description/DateCreated=Date Scanned:', font: font_small_bold_right, vertical: align_top);
date_static_text(fbname: '$$$/AWS/FileInfoLib/Panels/Description/DateCreated=Date Scanned', name: '$$$/AWS/FileInfoLib/Panels/DateCreated=Created', xmp_path: 'CreateDate', horizontal: align_fill, vertical: align_top, truncate: true, locked: true);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/CustomPanels/Genealogy/Provider=Provider:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Provider=Provider', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'Credit', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Credit', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/CustomPanels/Genealogy/Provenance=Provenance:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Provenance=Provenance', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Provenance', container_type: alt_struct, v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Provenance', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/DescriptionProvidedBy=Description Provided By:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/DescriptionProvidedBy=Description Provided By', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'DescriptionProvidedBy', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'DescriptionProvidedBy', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/DescriptionSurety=Description Surety:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/DescriptionSurety=Description Surety', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'DescriptionSurety', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'DescriptionSurety', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/CustomPanels/Genealogy/Description=Complete Subject Description:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Description=Complete Subject Description', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Description', container_type: alt_struct, v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Description', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/Caption=Informal Subject Description:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Caption=Informal Subject Description', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Caption', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Caption', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/MediaDescription=Media Description:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/MediaDescription=Media Description', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'MediaDescription', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'MediaDescription', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/Annotations=Annotations:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Annotations=Annotations', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Annotations', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Annotations', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/SpecialEditing=Special Editing/Alterations:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/SpecialEditing=Special Editing/Alterations', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'SpecialEditing', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'SpecialEditing', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/City=City/County:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/City=City/County', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'City', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'City', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/State=State:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/State=State', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'State', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'State', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/Country=Country:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Country=Country', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'Country', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Country', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/PhotoDate=Photo Date:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/PhotoDate=Photo Date', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'DateCreated', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'DateCreated', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/AWS/FileInfoLib/Panels/Description/Keywords=Keywords:',font: font_small_bold_right, vertical: align_top);
cat_container_edit_text(fbname: '$$$/AWS/FileInfoLib/Panels/Description/Keywords=Keywords',horizontal: align_fill, height: gTextViewHeight, xmp_path: 'Keywords', container_type: bag_struct, v_scroller: true);
mru_popup(xmp_path: 'Keywords', container_type: alt_struct, no_check: true, vertical: align_top);
</panel>

You are not going to be able to run your old system from the backup on this old computer as the hardware is incompatible.
You need to get a new computer or a refurbished one.

Info Panel Issues

Similar Messages

Maybe you are looking for