[OT] Plovdiv . . . / hard CASE
Somebody on this Use-List surmised that Plovdiv, Bulgaria might be rather like Madison, Wisconsin (or thereabouts). Going in search of a new PATA 160 GB disk (not that easy now that everybody except Richmond has gone SATA) I ended up parking my car next to this place: http://www.facebook.com/pages/Plovdiv/backside-cafe/153149382431 Had no time so didn't pop in for a drink; but fell for it instantly: I mean, with a name like that, who wouldn't . . . :) Tonight I am disciplining myself to work through my CASE problem; where a CASE loop goes AWOL when the stack becomes a standalone. Theories so far: 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 doesn't hold; so . . . Perhaps: case 101 if the vis of group CONZ is true then send mouseUp to img 2327k break end if if the vis of group CONZ is false then send mouseUp to img f2310.png break end if (err . . . tried that one last night; no joy) case 101 if the vis of group CONZ is true then send mouseUp to img 2327k break end if if the vis of group VWLZ is true then send mouseUp to img f2310.png break end if (groups CONZ and VWLZ flip their visibility back and forth) if this doesn't work I will go for a pair of off-screen images that VIS in-sync with the groups and pop them into the case statement. Will keep you posted. -- May yet end up walking across town to the Backside Cafe if things get too, too other . . . :( At least I might learn some Turkish; after all, having lived on-and-off for over 10 years in a town that was part of the Ottoman Empire for some 500 years, and where 25% of the population are either Turkish-speaking ethnic Turks or Turkish-speaking ethnic Romanies it is a little bit disgraceful I have not a word of Turkish. 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
Re: [OT] Plovdiv . . . / hard CASE
Richmond Mathewson wrote: Tonight I am disciplining myself to work through my CASE problem; where a CASE loop goes AWOL when the stack becomes a standalone. There's not enough info to say what's going wrong, but you'd save yourself a lot of time if you set a breakpoint near the top of the switch structure and step through it line by line. That would show you whether a case instance is executing or not, which line of the script isn't activating, what the state of the variables are, whether or not the engine thinks a group is visible, and so forth. Without that, it's just stabbing in the dark trying to guess what's happening. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ 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: [OT] Plovdiv . . . / hard CASE
Jacque- Tuesday, May 25, 2010, 10:25:49 AM, you wrote: There's not enough info to say what's going wrong, but you'd save yourself a lot of time if you set a breakpoint near the top of the switch structure and step through it line by line. That would show you Unless you've got some trick in mind I don't know about, that isn't going to help Richmond in a standalone... -- -Mark Wieder mwie...@ahsoftware.net ___ 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: [OT] Plovdiv . . . / hard CASE
Mark Wieder wrote: Jacque- Tuesday, May 25, 2010, 10:25:49 AM, you wrote: There's not enough info to say what's going wrong, but you'd save yourself a lot of time if you set a breakpoint near the top of the switch structure and step through it line by line. That would show you Unless you've got some trick in mind I don't know about, that isn't going to help Richmond in a standalone... Oh. Oops. Forgot it was a standalone thing. I guess the only recourse then is to sprinkle a bunch of answers into the code, i.e., case 101, got here, vis is true, etc. Or better, log all that to a text file. Richmond: there should be no difference between the visibility of a group in a stack and in a standalone, so I think something else is going on. My first impression was that running cross-platform would mean that the keycodes aren't the same across OSs, but if you're running the standalone on the same system you developed in, then that's not it. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ 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: [OT] Plovdiv . . . / hard CASE
On 25/05/2010 20:25, J. Landman Gay wrote: Richmond Mathewson wrote: Tonight I am disciplining myself to work through my CASE problem; where a CASE loop goes AWOL when the stack becomes a standalone. There's not enough info to say what's going wrong, but you'd save yourself a lot of time if you set a breakpoint near the top of the switch structure and step through it line by line. That would show you whether a case instance is executing or not, which line of the script isn't activating, what the state of the variables are, whether or not the engine thinks a group is visible, and so forth. Without that, it's just stabbing in the dark trying to guess what's happening. Thanks so much; you caught me before the time I would have wasted had I not had your advice. 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
Re: [OT] Plovdiv . . . / hard CASE
On 25/05/2010 20:30, Mark Wieder wrote: Jacque- Tuesday, May 25, 2010, 10:25:49 AM, you wrote: There's not enough info to say what's going wrong, but you'd save yourself a lot of time if you set a breakpoint near the top of the switch structure and step through it line by line. That would show you Unless you've got some trick in mind I don't know about, that isn't going to help Richmond in a standalone... The problem; very simply stated is that the CASE loop works 100% in a stack; but when built into a standalone does not. So I will have to muck around with alternative ways of doing the same thing (and in RunRev . . . Thank the Lord . . . there are many, many ways) and, each time, build a standalone and see if the thing still works. ___ 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: [OT] Plovdiv . . . / hard CASE
On 25/05/2010 20:40, J. Landman Gay wrote: Mark Wieder wrote: Jacque- Tuesday, May 25, 2010, 10:25:49 AM, you wrote: There's not enough info to say what's going wrong, but you'd save yourself a lot of time if you set a breakpoint near the top of the switch structure and step through it line by line. That would show you Unless you've got some trick in mind I don't know about, that isn't going to help Richmond in a standalone... Oh. Oops. Forgot it was a standalone thing. I guess the only recourse then is to sprinkle a bunch of answers into the code, i.e., case 101, got here, vis is true, etc. Or better, log all that to a text file. Richmond: there should be no difference between the visibility of a group in a stack and in a standalone, so I think something else is going on. My first impression was that running cross-platform would mean that the keycodes aren't the same across OSs, but if you're running the standalone on the same system you developed in, then that's not it. I'm testing on the Mac PPC I'm developing on. I'm off to have supper (Yup; 9.15 over here in the Wild East) and then boogie on down; shame, though, really, I lost track of my leopard-skin posing briefs years ago: really used to help with the coding . . . :) ___ 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: [OT] Plovdiv . . . / hard CASE
On 25/05/2010 20:40, J. Landman Gay wrote: Mark Wieder wrote: Jacque- Tuesday, May 25, 2010, 10:25:49 AM, you wrote: There's not enough info to say what's going wrong, but you'd save yourself a lot of time if you set a breakpoint near the top of the switch structure and step through it line by line. That would show you Unless you've got some trick in mind I don't know about, that isn't going to help Richmond in a standalone... Oh. Oops. Forgot it was a standalone thing. I guess the only recourse then is to sprinkle a bunch of answers into the code, i.e., case 101, got here, vis is true, etc. Or better, log all that to a text file. You know that sometimes (just sometimes, mind) I am a bit slow to think my way round things . . . Now in my 'Devawriter' I have the same problem with groups and their VIS being flipped; So: cracked open the stack and found (I mean, how come I am so flaming thick that after a matter of about 3 months I had forgotten how I effected that) that there is absolutely no reference to the VIS of a groups into which my faux buttons (images) are grouped; but to the VIS of an image outwith the group which has its visibility set to be the same as the group. Why? Probably stupid Richmond encountered the same problem just before Christmas . . . . . :( Listening to Peter Sarstedt: http://www.petersarstedt.com/ ___ 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: [OT] Plovdiv . . . / hard CASE
On 25/05/2010 20:40, J. Landman Gay wrote: Mark Wieder wrote: Jacque- Tuesday, May 25, 2010, 10:25:49 AM, you wrote: There's not enough info to say what's going wrong, but you'd save yourself a lot of time if you set a breakpoint near the top of the switch structure and step through it line by line. That would show you Unless you've got some trick in mind I don't know about, that isn't going to help Richmond in a standalone... Oh. Oops. Forgot it was a standalone thing. I guess the only recourse then is to sprinkle a bunch of answers into the code, i.e., case 101, got here, vis is true, etc. Or better, log all that to a text file. Richmond: there should be no difference between the visibility of a group in a stack and in a standalone, so I think something else is going on. My first impression was that running cross-platform would mean that the keycodes aren't the same across OSs, but if you're running the standalone on the same system you developed in, then that's not it. I have just tried all possible combinations within the Card script; all that work in the stack. Each time; on building a standalone the script fails. So; what I shall do, is start a new stack that includes those 2 groups and the card script and see if that works; and build up my stack from that. Very, very queer indeed. ___ 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
