Just discovered a trick I didn't know about. This is in the IDE, BTW.
I needed to have the first card of one of my stacks as the current
card, while I do something from another stack (a utility stack). If I
go card 1 of stack stackName then the stack stackName comes to
the front, but I
I wonder if that triggers an openCard event?
Bob
On Mar 4, 2011, at 10:05 AM, Peter Brigham MD wrote:
Just discovered a trick I didn't know about. This is in the IDE, BTW. I
needed to have the first card of one of my stacks as the current card, while
I do something from another stack (a
On 3/4/11 12:38 PM, Bob Sneidar wrote:
I wonder if that triggers an openCard event?
No. I don't think it triggers any messages.
Bob
On Mar 4, 2011, at 10:05 AM, Peter Brigham MD wrote:
Just discovered a trick I didn't know about. This is in the IDE, BTW. I needed to have the first card
It appears not to trigger openCard.
FYI, the reason that I needed to do this is that I am trying to do
something with long id's and found what seems to be a bug in how the
engine handles this. If I do this while on the first card of the stack:
put the long id of control 76 of card 1 of
Is the field a part of a background group? A background group belongs to a
stack, not to a card. (I might be wrong but I doubt it ;-) Also try:
send put the long id of control 76 to card 1 of stack myStack
get the result
What does that produce?
Bob
On Mar 4, 2011, at 11:04 AM, Peter Brigham
On Mar 4, 2011, at 2:17 PM, Bob Sneidar wrote:
Is the field a part of a background group? A background group
belongs to a stack, not to a card. (I might be wrong but I doubt
it ;-)
belongs to is what sense? The owner of the background group is the
card. Can you say what you mean
