Thanks. Hidden has all of the communication between script and plugin code in it also.  Surprised they didn't include the jsx code. RONC ... View more

Anyone see a Hidden.jsx to match the Hidden.cpp from: /pluginsdk/samplecode/filter/hidden/?  Seems like that would have been included with the source code for the plugin. Thanks, RONC ... View more

JJ, As usual you have workable way to do what I want. Thanks, RONC ... View more

r-bin, Thanks for you time and effort.  I think that I can handle making a **Hidden** plugin. Cheers, RONC ... View more

Looks interesting.  By chance do you have the source code for the interpolate.8bf? Thanks. RONC ... View more

There is an option to HIDE plug-ins when writing them.  The plug-in "category" parameter needs to be **Hidden** and they won't appear in filter menu but can be executed by scripts and actions I'm told.  I have the plug-in hiding and am working on script with action to follow if I learn how. Adobe hid something from you "The Angie." RONC ... View more

Thanks for your response. I should have made some comments in the initial readme about what my aims were in doing this project.  First, I was helping Jonas to get his action to work.  So I needed to fix the Fourier transform (Ft) code to give him and the users a good input and output as the present code was broken.  I looked at the code and noticed several errors related to Ft and others to working in Photoshop plugin.  I set out just to modify Alex's original code and found that it was in simple C not C++ and then decided I could do it.  Not being a C or C++ programmer (actually I'm a research physicist and used Ft extensively) it was going to be a major chore.  Secondly I wanted to supply the Photoshop Users with Ft implementations that are easy for them to use.  This includes diagnostics which are part of the Suite. I called around for programming help and none appeared so it all mine and the patient people at a few websites.  Being the physicist, I knew that I needed to generate code to do 1D, 2D, and 3D transforms.  Forward and inverse for each of those.  All needed to handle 8, 16, and 32 bit/color channel.  I set out to code one plugin to do any combination of the needs but soon found other constraints the would make me really learn C/C++ and learn Photoshop plugins with little or no documentation available.  I stepped back and decided to write one very simple plugin to do what Alex's code set out.  I actually found that the forward and inverse algorithm were very similar and combined the two into one source but compiled separately.  Finally we hooked it in the action and we stepped through what was happening and changed the format of spectra so it was easier to use.  After a while I had cloned the first plugin into forward and inverse by the 3 dimensions.  Started to think about run times and decided to make more clones where the Half width transform were computed and thereby reducing wall clock time by about 50%.  So I ended up with 12 very simply coded plugins which could be used individually in Photoshop.  Other than coding, I ran C Lint and other diagnostics to finalize the code.  There should be no unused variables or uninitalized variables.  Code is indented for easier reading. There are no parameters needed from the user so having a dialog would have been of no use and makes use within an action much better.  Using properly compiled plugins can be inner mixed between Windows and Mac as well as different computers of each type.  Jonas and I had a person, Francesco Pierfederici, with Mac programming experience to join us to make the code run on Mac Photoshop installs.  The exact ccp are used on Windows and Mac.  Other files necessary for compiling are in folder and again are the same for Win or Mac unless noted. In the end the code I produced is not 2018 state of the art code but there is no reason for it to be.  My major aim was to make User-friendly Ft suite that was very versatile and software that can be viewed by both programming novices and science types who want to know how you do Ft on a computer using Photoshop.  I plan to lock my final code and change only for bug fixes.  Anyone who wishes to play with the code, branch off from the GIT code and you be responsible for the usage. I'm willing to discuss the plugins and what they do but not programming style etc.  These routines are for the Photoshop USERS. RONC ... View more

Comments please during your perusal.  Need a lot of help with documentation as I'm not sure what needs to be added. Use plugins only through FtFourierTransformSuite script not from Filter menu. RONC ... View more

This version of the Fourier transform plugins includes: 8, 16, and 32 bit/color channel RGB individual channels (not desaturated) 1D, 2D, and 3D Half and Full spectrum transforms. They all are open-source and use the FFTw software for the transforms.  The individual transforms should be applied only using the Ft  Fourier Transform Suite script rather than from the Filter menu as a standard RGB file cannot hold the amount of data generated.   Windows and Mac with Photoshop CS6 through CC present (2018). These are being loaded to   GitHub - rechmbrs/FtPattern: Ft Fourier transforms C++ code for Photoshop WinMac and Pattern Suppression Action    but it is not complete yet.  Presently working on documentation and history.  Need persons to read docs and ask question to fill in missing documentation.  Help will be accepted if you have time. RONC ... View more

Have a look at this Programming plugins for Photoshop: Building a plug-in .  Also view any vcxproj file in the samples within the the SDK. RONC ... View more

Background layers are a terrible problem in using Actions to Scripts development.  Often the ExtendScript coder has no idea what kind of file the Action used to build it.  But Actions seem to work with or without the BGlayer.  We now know how to build the Actions without using the Layers panel but old ones are hit and miss. For Plugins, we flatten then un-flatten the input before continuing. RONC ... View more

With the help of a centrifuge, I think I undissolved the code you were referring to. Thanks Tom and JJ. RONC ... View more

Works like a charm. Thanks, RONC ... View more

It does work on 32 bpc data very well.  Just need to display the histograms. RONC ... View more

JJ, Thanks for the response. I failed to mention that the user interface is in the script which is driving 40 or so plugins.  Most of the plugins do not have need a dialog but a couple have now matured to the point they need info from the previously executed plugins and some number crunching in the script. Is there a place in the Global Parameters that we can store like 64 bytes of info for the next plugin to view?  Part of the 64 bytes would be for security of getting correct info. I coded a external file method for a quick test and it works OK.  I saved the file in %TEMP% and delete it after I get the info from it.  I'd sure prefer to do it internally with the script and plugins. I'm always paddling upstream as it more interesting. RONC ... View more

Will this work on 32 bpc floating point data?  If not, is there a quick workaround? Thanks, RONC ... View more

JJ, Thanks. So the final words are to put the updated jsx/jsxbin or a short cut from it in your Photoshop script folder (  C:\Program Files\Adobe\Adobe Photoshop CC 2018\Presets\Scripts\  ).  When looking for it in the Filter menu, the script will be at the very bottom of the list. RONC ... View more

JJ, Thanks a lot.  This will be very helpful once I get a couple more questions answered. Once inserted into the script, where is the script file stored?  Scripts or plugins folders for Photoshop to find?  Should <Name> contain anything special?  Like a filename with .8bf extension??  Is this part of a PIPL?  Anything else so we don't have to bug again? I appreciate your help in finding these hidden gems. RONC ... View more

Tom, You got through to me on this.  I found that there is Version Info section of the .rc file.  This section is defined by Microsoft for general use relating version information of not only software but anything.  See also Plugin with "NO VERSION" . RONC ... View more

Tom, I'm losing my ability to translate from Dissolve to reality.   I have not dialog so About is not included in my code. Help>System Info gives me XXXX,8bf   NO VERSION ..............     My XXXX is a simple title like MATH   I have found nothing in Dissolve.r relating to VERSION  which I would like to be MATHv1.02.01. I can't see where the Version would be inserted.  I've read every Adobe PIPL article that looked like it might help me. Dissolve doesn't make for good documentation!!!! Regards, RONC Here is the latest Dissolve.r installed by Adobe to my PC: // ADOBE SYSTEMS INCORPORATED // Copyright  1993 - 2002 Adobe Systems Incorporated // All Rights Reserved // // NOTICE:  Adobe permits you to use, modify, and distribute this // file in accordance with the terms of the Adobe license agreement // accompanying it.  If you have received this file from a source // other than Adobe, then your use, modification, or distribution // of it requires the prior written permission of Adobe. //------------------------------------------------------------------------------- #include "PIDefines.h" #ifdef __PIMac__ #include <Carbon.r> #include "PIGeneral.r" #include "DissolveScripting.h" #include "PIUtilities.r" #elif defined(__PIWin__) #define Rez #include "DissolveScripting.h" #include "PIGeneral.h" #include "PIUtilities.r" #endif #include "PIActions.h" resource 'PiPL' ( 16000, "Dissolve", purgeable ) { { Kind { Filter }, Name { plugInName "..." }, Category { vendorName }, Version { (latestFilterVersion << 16 ) | latestFilterSubVersion }, Component { ComponentNumber, plugInName }, #ifdef __PIMac__ CodeMacIntel64 { "PluginMain" }, #else #if defined(_WIN64) CodeWin64X86 { "PluginMain" }, #else CodeWin32X86 { "PluginMain" }, #endif #endif SupportedModes { noBitmap, doesSupportGrayScale, noIndexedColor, doesSupportRGBColor, doesSupportCMYKColor, doesSupportHSLColor, doesSupportHSBColor, doesSupportMultichannel, doesSupportDuotone, doesSupportLABColor }, HasTerminology { plugInClassID, plugInEventID, 16000, plugInUniqueID }, EnableInfo { "in (PSHOP_ImageMode, RGBMode, GrayScaleMode,"              "CMYKMode, HSLMode, HSBMode, MultichannelMode," "DuotoneMode, LabMode, RGB48Mode, Gray16Mode) ||" "PSHOP_ImageDepth == 16 ||" "PSHOP_ImageDepth == 32" }, PlugInMaxSize { 2000000, 2000000 }, FilterLayerSupport {doesSupportFilterLayers}, FilterCaseInfo { { /* Flat data, no selection */ inWhiteMat, outWhiteMat, doNotWriteOutsideSelection, filtersLayerMasks, worksWithBlankData, copySourceToDestination, /* Flat data with selection */ inWhiteMat, outWhiteMat, writeOutsideSelection, filtersLayerMasks, worksWithBlankData, copySourceToDestination, /* Floating selection */ inWhiteMat, outWhiteMat, writeOutsideSelection, filtersLayerMasks, worksWithBlankData, copySourceToDestination, /* Editable transparency, no selection */ inWhiteMat, outWhiteMat, doNotWriteOutsideSelection, filtersLayerMasks, worksWithBlankData, copySourceToDestination, /* Editable transparency, with selection */ inWhiteMat, outWhiteMat, writeOutsideSelection, filtersLayerMasks, worksWithBlankData, copySourceToDestination, /* Preserved transparency, no selection */ inWhiteMat, outWhiteMat, doNotWriteOutsideSelection, filtersLayerMasks, worksWithBlankData, copySourceToDestination, /* Preserved transparency, with selection */ inWhiteMat, outWhiteMat, writeOutsideSelection, filtersLayerMasks, worksWithBlankData, copySourceToDestination } } } }; resource 'aete' (16000, "Dissolve dictionary", purgeable) { 1, 0, english, roman, /* aete version and language specifiers */ { vendorName, /* vendor suite name */ "Adobe example plug-ins", /* optional description */ plugInSuiteID, /* suite ID */ 1, /* suite code, must be 1 */ 1, /* suite level, must be 1 */ { /* structure for filters */ plugInName, /* unique filter name */ plugInAETEComment, /* optional description */ plugInClassID, /* class ID, must be unique or Suite ID */ plugInEventID, /* event ID, must be unique to class ID */ NO_REPLY, /* never a reply */ IMAGE_DIRECT_PARAMETER, /* direct parameter, used by Photoshop */ { /* parameters here, if any */ "amount", /* parameter name */ keyAmount, /* parameter key ID */ typeFloat, /* parameter type ID */ "dissolve amount", /* optional description */ flagsSingleParameter, /* parameter flags */ "disposition", // second parameter keyDisposition, // parameter key ID typeMood, // parameter type ID "dissolve disposition", // optional description flagsEnumeratedParameter, // parameter flags "ignore selection", /* optional parameter */ keyIgnoreSelection, /* key ID */ typeBoolean, /* type */ "filter entire image", /* optional desc */ flagsSingleParameter /* parameter flags */ } }, { /* non-filter plug-in class here */ }, { /* comparison ops (not supported) */ }, { /* any enumerations */ typeMood, /* type disposition 'mooD' */ { "clear", /* first value */ dispositionClear, /* 'moD0' */ "clear headed", /* optional description */ "cool", /* second value */ dispositionCool, /* 'moo1' */ "got the blues", /* optional description */ "hot", /* third value */ dispositionHot, /* 'moo2' */ "red-faced", /* optional description */ "sick", /* fourth value */ dispositionSick, /* 'moo3' */ "green with envy" /* optional description */ } } } }; ... View more

Thanks for the help.  After taking in all of the good information from you, we have the script working.  We broke it into portions and many of our problems went away.  Also decided to make the Action work to match script which will be much easier to understand for the users. I hit the jackpot with this group.  JJ always has a few that helps so many. My appreciation, RONC ... View more

I didn't remove the actual build of the steps.   I didn't send that part hoping it doesn't matter. Can't I do this by just save a variable to disk and not using getinv and setinv. Is there really a problem having true, true or false, false in a function call? RONC ... View more