Re: A nasty experience with the currentcard
On Sat, Feb 21, 2015 at 11:06 AM, Richard Gaskin ambassa...@fourthworld.com wrote: has this Dictionary omission been submitted to the bug queue Bug 14651 http://quality.runrev.com/show_bug.cgi?id=14651 Unfortunately, now I can't replicate the bug that led to this discussion in the first place. :-/ ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: A nasty experience with the currentcard
Thanks, I figured that out. It was only annoying because I was working on a stack named with a rev prefix, so no error messages were being thrown. On Sat, Feb 21, 2015 at 1:44 AM, Phil Davis rev...@pdslabs.net wrote: Try current card instead. go to current card of stack x put the customProperties[myData] of current card of stack x into tMyPropsA etc. It works. Phil Davis On 2/20/15 9:36 PM, Geoff Canyon wrote: It seems currentcard is undocumented. I don't even know where I came up with it. But it works in general: put the long id of the currentcard of the topstack works fine in the message box. It also works in the script of a button -- generally. As it turns out, the above will give an error *if* the button is in a palette stack, but not if it's in a toplevel stack. (at least in 6.7.1 on a mac) I can't really call it a bug since currentcard isn't in the dictionary. But it just cost me two hours of my life, so this my primitive yawp of frustration. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode -- Phil Davis ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: A nasty experience with the currentcard
I don't remember -- it could just be that I was going for current card and forgot the space. The script editor colors currentcard the same as terms like long id, while it colors current card like keywords like stack For me, LC 6.7.1 on a Mac (most recent OS): toplevel: put the long id of the current card of the topstack -- works put the long id of the currentcard of the topstack -- works palette: put the long id of the current card of the topstack -- works put the long id of the currentcard of the topstack -- error: button Button: execution error at line n/a (Chunk: can't find card), char 1 And of course I was working on Navigator, stack name revNavigator, so no error messages were thrown. It would be nice if there were a simple way to change the name of a stack, and all the behaviors that reference buttons in that stack. On Sat, Feb 21, 2015 at 1:39 AM, Richard Gaskin ambassa...@fourthworld.com wrote: Geoff Canyon wrote: It seems currentcard is undocumented. I don't even know where I came up with it. But it works in general: put the long id of the currentcard of the topstack works fine in the message box. It also works in the script of a button -- generally. As it turns out, the above will give an error *if* the button is in a palette stack, but not if it's in a toplevel stack. (at least in 6.7.1 on a mac) I can't really call it a bug since currentcard isn't in the dictionary. But it just cost me two hours of my life, so this my primitive yawp of frustration. I didn't know about currentCard so I just tried it - made a two stacks, the first opens the second as a palette, and the second has the statement shown above in a button's mouseUp handler. Works as expected. Also works with this card. LC 6.7.2, Ubuntu 14.04 If currentCard is undocumented what prompted you to try it? Does it work with this card? -- Richard Gaskin Fourth World Systems Software Design and Development for Desktop, Mobile, and Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: A nasty experience with the currentcard
It was in one of the release notes many versions ago. I actually used it in a project once. You can set the currentcard of another stack without having to go there, which is handy for some situations. On February 21, 2015 1:59:08 AM CST, Geoff Canyon gcan...@gmail.com wrote: I don't remember -- it could just be that I was going for current card and forgot the space. The script editor colors currentcard the same as terms like long id, while it colors current card like keywords like stack For me, LC 6.7.1 on a Mac (most recent OS): toplevel: put the long id of the current card of the topstack -- works put the long id of the currentcard of the topstack -- works palette: put the long id of the current card of the topstack -- works put the long id of the currentcard of the topstack -- error: button Button: execution error at line n/a (Chunk: can't find card), char 1 And of course I was working on Navigator, stack name revNavigator, so no error messages were thrown. It would be nice if there were a simple way to change the name of a stack, and all the behaviors that reference buttons in that stack. On Sat, Feb 21, 2015 at 1:39 AM, Richard Gaskin ambassa...@fourthworld.com wrote: Geoff Canyon wrote: It seems currentcard is undocumented. I don't even know where I came up with it. But it works in general: put the long id of the currentcard of the topstack works fine in the message box. It also works in the script of a button -- generally. As it turns out, the above will give an error *if* the button is in a palette stack, but not if it's in a toplevel stack. (at least in 6.7.1 on a mac) I can't really call it a bug since currentcard isn't in the dictionary. But it just cost me two hours of my life, so this my primitive yawp of frustration. I didn't know about currentCard so I just tried it - made a two stacks, the first opens the second as a palette, and the second has the statement shown above in a button's mouseUp handler. Works as expected. Also works with this card. LC 6.7.2, Ubuntu 14.04 If currentCard is undocumented what prompted you to try it? Does it work with this card? -- Richard Gaskin Fourth World Systems Software Design and Development for Desktop, Mobile, and Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: A nasty experience with the currentcard
Sorry if I'd missed this earlier, but has this Dictionary omission been submitted to the bug queue? When we kick-off the Community Documentation Team soon I'd like to make sure we catch things like this. J. Landman Gay wrote: It was in one of the release notes many versions ago. I actually used it in a project once. You can set the currentcard of another stack without having to go there, which is handy for some situations. On Sat, Feb 21, 2015 at 1:39 AM, Richard Gaskin wrote: If currentCard is undocumented what prompted you to try it? Does it work with this card? -- Richard Gaskin Fourth World Systems Software Design and Development for Desktop, Mobile, and Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: A nasty experience with the currentcard
Try current card instead. go to current card of stack x put the customProperties[myData] of current card of stack x into tMyPropsA etc. It works. Phil Davis On 2/20/15 9:36 PM, Geoff Canyon wrote: It seems currentcard is undocumented. I don't even know where I came up with it. But it works in general: put the long id of the currentcard of the topstack works fine in the message box. It also works in the script of a button -- generally. As it turns out, the above will give an error *if* the button is in a palette stack, but not if it's in a toplevel stack. (at least in 6.7.1 on a mac) I can't really call it a bug since currentcard isn't in the dictionary. But it just cost me two hours of my life, so this my primitive yawp of frustration. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode -- Phil Davis ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: A nasty experience with the currentcard
Geoff Canyon wrote: It seems currentcard is undocumented. I don't even know where I came up with it. But it works in general: put the long id of the currentcard of the topstack works fine in the message box. It also works in the script of a button -- generally. As it turns out, the above will give an error *if* the button is in a palette stack, but not if it's in a toplevel stack. (at least in 6.7.1 on a mac) I can't really call it a bug since currentcard isn't in the dictionary. But it just cost me two hours of my life, so this my primitive yawp of frustration. I didn't know about currentCard so I just tried it - made a two stacks, the first opens the second as a palette, and the second has the statement shown above in a button's mouseUp handler. Works as expected. Also works with this card. LC 6.7.2, Ubuntu 14.04 If currentCard is undocumented what prompted you to try it? Does it work with this card? -- Richard Gaskin Fourth World Systems Software Design and Development for Desktop, Mobile, and Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
