Thanks, Klaus, for getting back to me about my Windows standalone issue.
Making a standalone that works in Windows has been such a problem for me! I can't believe there's not more uproar about this. Stuff just doesn't work like it's supposed to and often the symptoms don't help you pinpoint the cause.
Anyway, I implemented your idea. Specifically I wrote send "parttwo" to btn "instructions" of cd 1 of this stack
Is this okay? (Because I couldn't figure out the name of my stack, stupid as that my sound. When I typed "answer the stack name" and such things, I just got errors.)
Anyway, the problem still persists with my standalone. But perhaps it was a different problem to begin with. The weird thing is, before I implemented this change it seemed like the standalone was only reading the first portion of my script, not the second (like I described before). WITH this change, it's not working at all.
I don't see why a parameter is preferable over a global variable, but I implemented that suggestion anyway. It worked fine in the development environment, but again no nothing on the windows standalone. Perhaps there is some other error going on, but I can't figure it out at all.
Again, the symptom is that the Windows standalone won't put text in the card field like its supposed to, but I suspect that might be symptomatic of something unrelated since that's been the case with other Windows standalone problems that I've had.
Sorry for the pestering. I really appreciate your help! Andrew
On Wednesday, December 8, 2004, at 09:00 AM, [EMAIL PROTECTED] wrote:
Hi Andrew,
I've got another clue about why my windows standalone is not working. Okay, my script into two halves-- one in the card script and one in the script of a button. At the end if the card script section it says send parttwo to card button "instructions"
...And I made sure to put all of the relevant local variables (only 1) into a global variable, so that it could be accessed in the script of the card button "instructions".
You could even send that local var as a parameter to your button, see below...
However, It seems as though my standalone is only running the card script section, and then not going to the script of cd btn "instructions". Is there any known error that Windows standalones have with, as in this case, one handler calling a handler that's located elsewhere?
If you specify the exact location of the button it will work!
Like: ... send "parttwo" to btn "name here" of cd x ## of stack y ## if the button is inanother stack... ...
Please note the quotes!
Or with the above mentioned parameter:
local varname
on xyz send "parttwo varname" to btn "name here" of cd x ...
And in the button:
on parttwo whattheheck ## do something with whattheheck ...
Make sure that "varname" is not empty! ;-)
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
