Coming unstuck with standalones: a real head CASE
I have been working recently on a teacher version (wrongly called 'Pro') of my Devawriter program for Sanskrit. Feeling reasonably smug (Hey-Ho, pride comes before the fall) I sent some standalones labelled 'Beta' off, down the pipe, to my Beta testers; only to recieve a fairly forthright answer that the thing didn't work properly ! Cracked out the standalone, and it DIDN'T . . . :( Went back to the stack, and it DID . . . the mystery thickens . . . SO; what's going wonky??? A tediously long SWITCH routine; on rawKeyDown RAWK set the useUnicode to true switch RAWK --- buckets more CASE stuff here case 101 if the vis of group CONZ is true then send mouseUp to img 2327k break else send mouseUp to img f2310.png break end if --- buckets more CASE stuff here default pass rawKeyDown end switch end rawKeyDown In the stack, when the group CONZ is not visible the latter half of the CASE statement 'fires', In a standalone, when the CONZ is not visible the latter half of the CASE statement DOESN'T WORK. Poo, Poo, Poo! --- Moronically speculative interlude. Maybe standalones don't behave themselves re the VIS of groups?? --- Advice, recommendations, help gratefully received; Please, Please, pretty Please! Richmond Mathewson. ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Coming unstuck with standalones: a real head CASE
In the stack, when the group CONZ is not visible the latter half of the CASE statement 'fires', In a standalone, when the CONZ is not visible the latter half of the CASE statement DOESN'T WORK. No wonderful ideas, but are you sure the group CONZ is really invisible, or is it inside another group that is invisible? That's a trap that has caught me before, although I would expect it to behave the same in the IDE as in a standalone. Another possibility: could there be two groups with the same name? Maybe they are re-ordered in the standalone, so the script is looking at the wrong one. Cheers, Sarah ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Coming unstuck with standalones: a real head CASE
On 24/05/2010 14:58, Sarah Reichelt wrote: In the stack, when the group CONZ is not visible the latter half of the CASE statement 'fires', In a standalone, when the CONZ is not visible the latter half of the CASE statement DOESN'T WORK. No wonderful ideas, but are you sure the group CONZ is really invisible, or is it inside another group that is invisible? Just checked: the card had 2 groups; CONZ and VWLZ; when CONZ is invisible it is invisible, rather than as you suggest. That's a trap that has caught me before, although I would expect it to behave the same in the IDE as in a standalone. Well so would I; one of the reasons I am so mystified. Another possibility: could there be two groups with the same name? Maybe they are re-ordered in the standalone, so the script is looking at the wrong one. I will probably have to ungroup the group and set the VIS on all its components individually, curses, curses, curses. Cheers, Sarah Thanks for your ideas. You are lucky, there in Australia, as your winter approaches: here in Bulgaria we are just starting our hot and sticky patch rising to 48 degs C and humid that lasts from now until mid-September! sincerely, Richmond. ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
