LiveCode Forums.

When tabbing into some fields, I need the text to be highlighted. The following code does this, however, there's an annoying flicker which occurs. It appears that the cursor first gets positioned at the end of the text then the text gets highlighted, thus the "flicker". Is there a way around this?

Thanks

Hi Bill,

instead of using the openField message, use the tabkey message. Of course, you will have to write a different script for each field or apply some trick with cursom properties.
Best,

Mark

That approach is not practical. It also doesn't help with tabbing backward (shift-tab). Anyway, I'll just deal with the flicker and post a QCC report. Thanks anyway.

Mark wrote:Hi Bill,

instead of using the openField message, use the tabkey message. Of course, you will have to write a different script for each field or apply some trick with cursom properties.

Code: Select all

on tabKey
  select text of fld "Next Field"
end tabKey

Best,

Mark

Hi Bill,

Why is't it practical? You have to write a script to make it practical. You can expect that Rev does everything for you.

You didn't say you want it to go the reverse if the shiftkey is pressed. You can check whether the shiftkey is pressed in your script and select the text of a different field.

Best,

Mark

More importantly, what operating system/environment do you have? There's various quirks in the display (that for instance, lockscreen doesn't prevent, although I believe it should) on my runtimes in various ways, but I get no flicker at all in testing your original openField script.
Granted, it's only one card, but I made several very large fields and they all tabbed and selected with no quirk in the display.
I use Rev Studio 3 on Windows XP, mainly.

bill,
this works if you put it into the script of a card (based on Marks suggestion) almost no flicker with this. Although the flicker is barely noticeable on my Mac 2.2 Mhz. Give your user a nickel if he notices the flicker (as an incentive)
bernd

Hi bn,

I applied your code but I must press tab key two times then cursor moves to another field.

Plz help me. Thanks

You can also let the engine do the hiliting whenever the user 'tabs' between fields. Select your field, open the Inspector and tick the checkbox 'Tab on return' in the 'Basic properties' panel - or if you'd rather do it by script HTH,

Jan Schenkel.

It's OK now. Thanks

Jan Schenkel wrote:

You can also let the engine do the hiliting whenever the user 'tabs' between fields. Select your field, open the Inspector and tick the checkbox 'Tab on return' in the 'Basic properties' panel - or if you'd rather do it by script

that works perfectly, without the hassle of scripting the tab or openfield and Bill, no FLICKER.

Bernd

Hi,

That's a great solution, but note that the field layers have to be in a particular order for this to work.

Best,

Mark

Thanks Jan. Odd, but, that works! How do you know this stuff? I guess you stumbled on it one day?

While it shouldn't be an issue for most of my fields, losing the ability to use the Return key to generate a carriage return within a field may be a concern (for larger text fields). But, as that may be the exception rather than the norm, other techniques could be used for that.

But, regardless, your technique provides the highlight without flicker nice and easy.

Thanks!

Bill

Janschenkel wrote:You can also let the engine do the hiliting whenever the user 'tabs' between fields. Select your field, open the Inspector and tick the checkbox 'Tab on return' in the 'Basic properties' panel - or if you'd rather do it by script

Code: Select all

set the autoTab of field "foobar" to true

HTH,

Jan Schenkel.

I'm not even sure where I got that information - it must have come up on the use-revolution list at one point and it stuck in my head (which is odd, as I usually have the memory of a goldfish)

It's a funky property, as it allows the user to only enter a return if it doesn't cause the field to 'scroll' - so if you have a field that is tall enough to hold 4 lines of text, then the user can enter up to 4 lines of text and the next time he hits the return key the focus will jump to the next field.

But the jump to the next field and the hiliting behaviour is great for data entry forms as you don't have to go about and script individual 'tabKey' and 'returnInField' handlers to move things on their merry way.

Jan Schenkel.

Excellent. Thanks for the clarification on the return key. Awesome tips here. They're now in my personal RR notes db.

Thanks

Bill

Janschenkel wrote:I'm not even sure where I got that information - it must have come up on the use-revolution list at one point and it stuck in my head (which is odd, as I usually have the memory of a goldfish)

It's a funky property, as it allows the user to only enter a return if it doesn't cause the field to 'scroll' - so if you have a field that is tall enough to hold 4 lines of text, then the user can enter up to 4 lines of text and the next time he hits the return key the focus will jump to the next field.

But the jump to the next field and the hiliting behaviour is great for data entry forms as you don't have to go about and script individual 'tabKey' and 'returnInField' handlers to move things on their merry way.

Jan Schenkel.