Re: first field to get keyboard focus?
Sarah writes: [snip] I don't know the reason for this although it might be that Rev stores the focus so that the same field is selected when you go to a new card. The workaround is to have a preOpenCard handler that specifically sets the focus to the correct field. e.g. focus on field 1 Cheers, Sarah Mr. Rice, Remember also that focus on field 1displays the cursor at the same position at which it was previously. To positon the cursor at the beginning/end of the field and have focus, use in the preOpencard handler select before/after field 1 miscdas ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: first field to get keyboard focus?
On Thursday, May 29, 2003, at 12:12 AM, Edwin Gore wrote: If another object overlays the field (like, the lable maybe?) it will not get focaus corrently. Try making sure that no other object overlays your field. Ah OK. There wasn't another control overlaying the field, but a *group* was. Tricky! Thanks, Alex Rice, Software Developer Architectural Research Consultants, Inc. [EMAIL PROTECTED] [EMAIL PROTECTED] ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: first field to get keyboard focus?
If another object overlays the field (like, the lable maybe?) it will not get focaus corrently. Try making sure that no other object overlays your field. - Original Message - From: "Alex Rice" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 28, 2003 11:44 PM Subject: Re: first field to get keyboard focus? > > On Wednesday, May 28, 2003, at 10:40 PM, J. Landman Gay wrote: > > > I think it's the lowest-numbered field that gets the automatic cursor > > insertion. Try relayering your fields and put the desired target as > > layer 1. > > > Sure enough. Thanks- I don't know why I thought it was front-to-back > (higher to lower layer number). > > Here's another question: do you know why some fields will appear to > have the blinking insertion point, but others will not (but do still > have the focus border?) Fields that otherwise seem identical seem to > have this behavior. I've seen only my smaller single-line fields do > this. > > Alex Rice, Software Developer > Architectural Research Consultants, Inc. > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > > > ___ > use-revolution mailing list > [EMAIL PROTECTED] > http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: first field to get keyboard focus?
On Wednesday, May 28, 2003, at 10:40 PM, J. Landman Gay wrote: I think it's the lowest-numbered field that gets the automatic cursor insertion. Try relayering your fields and put the desired target as layer 1. Sure enough. Thanks- I don't know why I thought it was front-to-back (higher to lower layer number). Here's another question: do you know why some fields will appear to have the blinking insertion point, but others will not (but do still have the focus border?) Fields that otherwise seem identical seem to have this behavior. I've seen only my smaller single-line fields do this. Alex Rice, Software Developer Architectural Research Consultants, Inc. [EMAIL PROTECTED] [EMAIL PROTECTED] ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: first field to get keyboard focus?
On Thursday, May 29, 2003, at 08:34 am, Alex Rice wrote: On a card I have a field with the highest layer number of all the controls. Nonetheless, *another* field is the one that gets the keyboard input cursor when I go to the card. Has anyone seen this and do you know what a workaround is? I think it's the lowest-numbered field that gets the automatic cursor insertion. Try relayering your fields and put the desired target as layer 1. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: first field to get keyboard focus?
I don't know the reason for this although it might be that Rev stores the focus so that the same field is selected when you go to a new card. The workaround is to have a preOpenCard handler that specifically sets the focus to the correct field. e.g. focus on field 1 Cheers, Sarah [EMAIL PROTECTED] http://www.troz.net/Rev/ On Thursday, May 29, 2003, at 08:34 am, Alex Rice wrote: On a card I have a field with the highest layer number of all the controls. Nonetheless, *another* field is the one that gets the keyboard input cursor when I go to the card. Has anyone seen this and do you know what a workaround is? Alex Rice, Software Developer Architectural Research Consultants, Inc. [EMAIL PROTECTED] [EMAIL PROTECTED] ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
first field to get keyboard focus?
On a card I have a field with the highest layer number of all the controls. Nonetheless, *another* field is the one that gets the keyboard input cursor when I go to the card. Has anyone seen this and do you know what a workaround is? Alex Rice, Software Developer Architectural Research Consultants, Inc. [EMAIL PROTECTED] [EMAIL PROTECTED] ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
