Carlos, Photoshop has a much older API where they call you and allow you to take over but provide a few call-backs that you have to hit from time-to-time to push the progress bar, retrieve image data, send image data back to the host, etc.
So to answer your questions: 1. No. I can make my own windows. As long as I clean up after myself, everything is fine. A plug-in is really a DLL with a different extension. It used to be that plug-ins were opened as needed and then closed afterwards, but for performance reasons, Adobe has started (say about CS4?) keeping the DLLs open. 2. No. Only one plug-in is supposed to be active at a time, so this condition can't happen. It is quite possible to make multiple plug-ins with the FLTK libraries, but two or more copies of Fl::run() will not be running at the same time. I know the Photoshop SDK really well (for anyone that cares) having written plug-ins with it since '94. It's based upon a Hypercard 'XCOD' style that was prevalent in the late 80's and has continued to grow/evolve/morph. There are many advantages to a modular design approach, of which one of my favorite is that extra APIs can be included so that the plug-ins can be used by more than one program. I'm deeply curious how you solved the problem. And what timezone are you in that you responded at 6:15am EDT? Thanks, -Chris > I might have some answers to your problem, but first I need to know a few > things: > > 1. Is Photoshop handling you a HWND of a window in which you have to build > your plugin´s GUI? (Actually, I´m sure the answer to this question doesn´t > really matter, but you never know...) > > 2. If you make a copy of your dll file with a different name (say, you end up > with plugin1.dll and plugin2.dll), can you have both plugins working at the > same time with their GUIs showing? (This is the question that matters) > > I have to say I have no experience with Photoshop plugins BUT I have > experience making audio plugins, which are also built as dll files. Some time > ago I tried to use FLTK as GUI library for audio plugins, and found the same > behaviour you are describing. After some time exploring both FLTK code and > the WIN32 API I managed to get it working and the solution is not that > complicated, although I must say I haven´t torture-tested it enough. Right > now I´m not at my dev PC so I don´t have my code at hand, but as soon as > you post an answer to the questions above I should be able to post > something more useful. > > Best regards, > > Carlos
_______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
