Re: me vs. this?

2005-08-07 Thread Charles Hartman
Yes, Cubist pointed this out too, and I've been mulling it over, and of course you're right. There's a logical this group, field, etc., when one is selected, clicked . . . But fleeting states aren't a good lexical basis for programming languages . . . Dynamic is good, but. Charles On Aug

Re: me vs. this?

2005-08-07 Thread Victor Eijkhout
On Aug 7, 2005, at 8:06 AM, Charles Hartman wrote: There's a logical this group, field, etc., when one is selected, clicked . . . So this makes sense in any piece of code that is in, or was called by a handler. V. ___ use-revolution

Re: me vs. this?

2005-08-06 Thread Jeanne A. E. DeVoto
At 11:20 AM -0400 8/5/2005, Charles Hartman wrote: Well, I don't know. Now that it's pointed out to me, I see in the Doc under 'this' only mentions of 'this card' and 'this stack' . . . It seems a little counterintuitive, though, doesn't it? to have an apparent plain English command with what

me vs. this?

2005-08-05 Thread Charles Hartman
In a mouseUp handler for a radio-button group called my group, I would have thought I could refer to the hilitedButtonName of the group without specifying it any further. But answer the hilitedButtonName doesn't give the right response. Neither does answer the hilitedButtonName of

Re: me vs. this?

2005-08-05 Thread Eric Chatonet
Hi Charles, Me is often opposed to the target: me is equivalent to the object that contains the currently running handler and the target refers to the object which received the message that started execution. Note that target without the refers to the contents of a control. When you use

Re: me vs. this?

2005-08-05 Thread xbury . cs
What I most don't understand (??) is the relation between me and this X when me is an instance of type X. Charles Charles me is used when an object queries it's own properties or objects. for example if i clicked in a field, the field script could ask: on mouseup get the hilitedline of

Re: me vs. this?

2005-08-05 Thread Jeanne A. E. DeVoto
At 10:09 AM -0400 8/5/2005, Charles Hartman wrote: What I most don't understand (??) is the relation between me and this X when me is an instance of type X. This only applies to the current card or current stack (this card or this stack). This may or may not be the object whose script is

RE: me vs. this?

2005-08-05 Thread MisterX
Jeanne Not just this stack and this card... Dont forget this group and this background... X -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeanne A. E. DeVoto Sent: Friday, August 05, 2005 16:48 To: How to use Revolution Subject: Re: me vs

Re: me vs. this?

2005-08-05 Thread Eric Chatonet
Hi Xavier, Could you give an example to explain how you refer to this group: I agree Jeanne a priori. And that's what the docs say... And if I understand well what can mean this card or this stack (the current stack, the current displayed card), I don't figure out what would mean this

Re: me vs. this?

2005-08-05 Thread Charles Hartman
: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeanne A. E. DeVoto Sent: Friday, August 05, 2005 16:48 To: How to use Revolution Subject: Re: me vs. this? At 10:09 AM -0400 8/5/2005, Charles Hartman wrote: What I most don't understand (??) is the relation between me and this X when me

Re: me vs. this?

2005-08-05 Thread Cubist
sez [EMAIL PROTECTED]: Now that it's pointed out to me, I see in the Doc under 'this' only mentions of 'this card' and 'this stack' . . . It seems a little counterintuitive, though, doesn't it? to have an apparent plain English command with what feels like an arbitrary limitation on its