Gripes with Adobe scripting UI
Spent a lot of time trying to get fillPath() to work in a UI. Looked to be simple in the scripting guide but no luck. The sample script colorselector.jsx with the Bridge SDK claimed to have paths used in it. I couldn't find it. Maybe Adobe can't get it to work either. Tried a half-baked second approach to use a group and change the bg color. My main intent is to create a visual model of a print with borders that can be adjusted with sliders for the user to get a good idea of that they're going to get. Made a black group and a white group and got it to work in CS3. Went to work and tried it on CS4 and it completely fell apart. The stack order was different than CS3 and I could only get one color to show instead of the two I had in CS3. Can't figure out why Adobe made this much of a change with the scripting to cause this much change. We're having big issues with CS4 and custom XMP templates along with Flash extendscript interface due to some limit our company (I think) is placing on the use of ActiveX. So as Adobe is moving more towards the use of Flash/flex with their other programs, this is causing problems in companies like mine that have tight controls on program interaction.
Don't know if someone from Adobe actually reads these forums, but just want to vent and let them know that there maybe some bugs in their products.
