how to click at a link in a handler

[Jim Ault]

On 2/3/06 3:13 AM, "André.Bisseret" <Andre.Bisseret at inria.fr> wrote:

> So I placed the handler (a part of it), as a custom command, at the
> stack level and it works well. Thanks Jim, butŠ
> it remains that I don't understand why clicking at the foundloc of a
> link (in a handler) triggers this error message.

Glad you found an answer that works :-)

I have very little experience with 'click at'.  Perhaps this has been
Bugzilla'd and will be fixed in the future.

I would be interested to know what the field handler was before you broke it
apart.  My preference would have been to put the whole hander in the stack
script, but I am one the few that do this (perhaps the only one??). Ah, a
renegade revolutionary.  If I did things the correct way, I would probably
have lots of good paying work and money in the bank :-)

Jim Ault
Las Vegas


On 2/3/06 3:13 AM, "André.Bisseret" <Andre.Bisseret at inria.fr> wrote:

> 
> Le Thursday, 2 Feb 2006, à 21:43 Europe/Paris, Jim Ault a écrit :
> 
>> On 2/2/06 11:39 AM, "André.Bisseret" <Andre.Bisseret at inria.fr> wrote:
>>> Le Thursday, 2 Feb 2006, à 19:14 Europe/Paris, Jim Ault a écrit :
>>>> 
>>>> On 2/2/06 10:03 AM, "André.Bisseret" <Andre.Bisseret at inria.fr> wrote:
>>>>> find line 1 of fld "FoundCards"
>>>>>   click at the foundLoc
>>>>> 
>>>>> When they are in the script, It does what I want (the right card
>>>>> appears) but I get the error "click: expression is not a point" !??
>>>>> 
>>>> If you know what the link does, why not just execute that step and
>>>> forget
>>>> about clicking on the link?
>>> It's because, in fact, a click on a link of the list of cards does not
>>> only show the corresponding card to the user but does others actions
>>> on
>>> this card (looking for keywords, highlighting them by setting their
>>> backgroundColor, making visible a button (which allow to set the
>>> backgroundColor to empty, Š).
>>> So I would like to simply click on the link to avoid to duplicate the
>>> scripting of these actions.
>>> 
>>> Thanks for your kind attention
>>> André
>> I guess my point is that if the link click initiates some handler or
>> set of
>> actions, why not just call that handler directly?  Maybe I just don't
>> understand what your link actually does when you click it.
>> 
>> Maybe I should ask...
>> Is the link click calling a handler?
> yes
>> If so, is the handler located at the field, card, or stack level?
> it was at the field level
>> Is the handler different for each line/field/card?
> no, it is the same for each line in the field
>> 
>> Placement of "the scripting of these actions" might make future
>> enhancements
>> easier and more powerful.
> So I placed the handler (a part of it), as a custom command, at the
> stack level and it works well. Thanks Jim, butŠ
> it remains that I don't understand why clicking at the foundloc of a
> link (in a handler) triggers this error message.
> well, I sleep well anyway :-)),  it is only one more mystery !
> all the best from Grenoble
> André
> 
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution