Re: A nasty experience with the currentcard

2015-02-21 Thread Geoff Canyon
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

Re: A nasty experience with the currentcard

2015-02-21 Thread Geoff Canyon
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

Re: A nasty experience with the currentcard

2015-02-21 Thread Geoff Canyon
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

Re: A nasty experience with the currentcard

2015-02-21 Thread J. Landman Gay
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

Re: A nasty experience with the currentcard

2015-02-21 Thread Richard Gaskin
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

Re: A nasty experience with the currentcard

2015-02-20 Thread Phil Davis
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.

Re: A nasty experience with the currentcard

2015-02-20 Thread Richard Gaskin
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