Printing Crashes Rev in OSX
Sivakatirswami
katir at hindu.org
Thu Feb 3 15:14:35 EST 2005
Ah... but that puts us back to original issue, Revolution *did* quit,
immediately after running the print job, even though the menuPick
parameter was only "Print" ... it processed the next case
on menuPick pWhichItem
switch pWhichItem
case "Print"
printTranscript
case "Quit"
save this stack
quit
break
end switch
end menuPick
# result: print job is done, Revolution quits
on menuPick pWhichItem
switch pWhichItem
case "Print"
printTranscript
break
case "Quit"
save this stack
quit
break
end switch
end menuPick
# result: print job done; Revolution stays alive.
??
Sivakatirswami
On Feb 2, 2005, at 3:11 PM, Dan Shafer wrote:
> In your specific case, it couldn't, of course, but the logic has to be
> built for situations where more than one case might apply to a given
> situation.
>
> Dan
>
> On Feb 2, 2005, at 3:17 PM, Sivakatirswami wrote:
>
>> Dan, Indeed, one would expect the drop-through if there is no "break"
>>
>> but, how would
>>
>> case "Quit"
>>
>> evaluate to "true" when the parameter
>> passed from the menuPick was "Print"
>> ??
>>
>> That's what is mysterious.
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
More information about the use-livecode
mailing list