That long bar across the desktop is what is seen when starting Apophymator in Apophysis 7X-15C, as of hotfix 7. That bar is a distorted version of the input dialog related to changes in Apo 7X 15C. Apophymator 10X hasn't changed and still runs the same on earlier 7X versions
Input dialogs for all scripts have been effected in 15C, but scripts that use complex input boxes like Apophymator suffer the most. Presently it's recommended to run Apophymator under Apo 7X 15B.
Input dialogs for all scripts have been effected in 15C, but scripts that use complex input boxes like Apophymator suffer the most. Presently it's recommended to run Apophymator under Apo 7X 15B.
:origin()/pre00/ee27/th/pre/f/2012/091/a/b/apophymator_startup_in_apophysis_7x_15c_by_morphapoph-d4um5w7.png)
I've examined the behavior and it is... outright weird. Now as we know here:
InputQuery('Title', 'Test'+#13#10, Variable);
Doesn't work as expected. I've tried it with sLineBreak and LineEnding instead but these aren't accepted at all.
There are more differences between the online references of Pascal I found and the way the scripter handles stuff. For example you can't mask the input by writing it like so:
InputQuery('Title', 'Test', TRUE, Variable);
Very confusingly I DID find a way to turn on masking anyway, and that is by having #0-#31 as the very first part in the second parameter, like this:
InputQuery('Title', #31+'Test', Variable);
That command will give an InputQuery with enabled masking. Any other version with #0 or #10 or so on would as well. More than that, whereas every time you put some '#xx' in somewhere it lengthens the box by one sign, if the first thing in the second parameter is #0-#31 then it won't lengthen the box but instead mask the input.
Now #32 would be a simple space and this:
InputQuery('Title', #32+'Test', Variable);
Would yield what we'd initially expect, the same if we'd write ' Test' instead.
I'm not sure if it's related to the issue, but it might be. After all the needed #10 and #13 are within the range of the 32 numbers that are being mistreated when put on the first spot.
I will surely look into this and thanks very much for your interest in investigating the problem.
Somewhere around DA is a comment George made to the effect that he contacted the TMS software people and they didn't have an explanation either.
So this looks very interesting.
Whoopie... motivation!!
Fred E
Could you tell with a quick glance if this might help with XP:
www.tmssoftware.com/site/vtd.a…
I saw something on the TMS site about "message boxes" (or similar) that related to changes beginning in Vista, but that's probably still not a solution for XP. Possibly what I saw was relevant but I'd have to search to find it. The major downside IIRC was that an additional component had to be purchased.
Just out of curiosity, I use #13#10 for linebreaks. Is there some other way to do that?
I happened to try on XP sp2, and I'll try again with sp3 when I have a chance.
I still think it's nothing I can do from the scripter.
I think the problem is with InputQuery('Title', 'Message', Variable) itself. (sorry for the lame terms).
There is no line break between the message and the area where a value is entered.
The effect can be seen in this script (if you perhaps can run XP in a VM):
morphapoph.deviantart.com/art/…
Don't worry too much. I just had a spare hour to test your suggestion so I gave it a shot.
Ordinarily I would see the text box beneath the Tests labels in your example; like this: morphapoph.deviantart.com/art/…
ps: do you know why I don't get short links anymore at DA? It used to be an auto thing. Big web sites ha' been gettin' me down lately with their rearranging stuff. "First it does it then it don't".
I think the DA links are sloppier now, but
I could never have guessed to try that though.
what George's upates would do to Apophymator.
The one and only problem I've seen so far is with the wonky dialogs. But those are due to some kind of upgrades that TMS-Software made to the new version George is using inside of 15c.
And everyone knows... it takes a while to get a handle on new bits of digits.
I have faith in George's ability. He's made some remarkable improvements to Apo.
FWIW, I would have given up on Apophymator had it not been for George's
willingness to implement multiple requests of mine which effected how the scripter worked.
With no Apophymator I would have been bored.
work with Apo in such a short time. So long as Apo works
I can live with wonky a dialogue box.
Hope to make some time this week for Apophymator. Tried
several attempts last month but the flame sequences
did'nt come out like I thought they would. I hope
to have something done soon though.