Just done a quick test with 4D Chart, seems to have the same issue, so I'm guessing this is standard behaviour ? Just seems odd I've not come across this more prominently in the documentation, unless I've missed it. Can anyone confirm this is normal and is it fixed in later versions of 4D (after 2003).
Steve4D wrote:
If on the form I use an interprocess var for my plug-in area name, i.e. <>MyArea, it is not set by my code but rather the process version is created and set, i.e. a var called MyArea is created and set. This causes problem when I subsequently pass <>MyArea as the reference to any of my functions as it's undefined. I'm using the standard PA_SetAreaReference( params, privateData ) to set my reference.
Why isn't it setting the correct interprocess variable and what can I do to sort this ?
I can work round it by using process vars but wondered whether this is standard behaviour or have I missed something ?
