Problem with Fields

[Dave]

Hi,

The thing is that this was working perfectly before RunRev version  
2.8.0.370 (the previous version I used was 350 I think). It also  
worked in 2.6.1.152.

So something must have changed, either in RunRev or as a result of  
other changes I have made. I was really trying to determine which?

All the Best
Dave

On 29 Mar 2007, at 01:24, Jim Ault wrote:

> On 3/28/07 5:04 PM, "Dave" <dave at looktowindward.com> wrote:
>>
>> I have a number of fields that the user can change. When they select
>> a field I want its old contents selected so that if they start to
>> type it overwrites the current contents. If they want to edit the
>> contents then they click again to de-select the text.
>>
>> I tried your suggestion and it worked! Not sure why though?
>>
>> The reason I added it without using the "send" command was because in
>> the documentation for "openField" it says:
>>
>> Examples:
>> on openField -- when clicking in the field, select all its text
>>    select text of the target
>> end openField
>>
>> Which is exactly what I want to do!
> There are other issues with events and messages...
>
> You might have to "lock messages" or deal with the traversal or  
> focusOut, or
> other events that could occur just after the openfield message is  
> sent.
> Perhaps you needed to "pass openfield" so that Rev will know that it
> happened.  Interface interactivity is not my area, so I am just  
> guessing
> here.
>
> The 'send' technique in effect says "let all other things happen, then
> select text"
>
> Jim Ault
> Las Vegas
>
>
>
> _______________________________________________
> 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