Skip to main content
S
sunny_chandel
Known Participant
July 30, 2010
Answered

Cursor Issue

  • July 30, 2010
  • 1 reply
  • 1432 views

Hi All
I have a cursor issue in my text flow.

The normal scenario is when the mouse cursor is over the text,   it is shaped as text cursor(like a vertical line in between two  horizontal lines) and when mouse moves and come out of text, it changed  to a pointer...this is the right behavior that mouse cursor should show.  

Now the problem...
when I made the text of  the text flow read only by selecting a entry from the combo box which  has other entries like read-select only,read - write both....If I place  the cursor inside the text after opening the combo box and then select  the read only option by using up arrow or down arrow and enter  key....the cursor become a text cursor permanently..i.e it does not  change when it moved out of text area and rolled over the buttons of the  component....which looks very ugly that a text cursor over the button  or any other component...it backs to its normal behaviour when I refresh.
Same problem is there if I use any key board shortcut  to make text read only.
You can see that when I am writing this question if mouse cursor is  over the text area it is text cursor and I am moving mouse to Post Message button...it changes to pointer....I think now the issue is  clear.

This topic has been closed for replies.
Correct answer robin_briggs

This sounds like a bug that was in TLF 1.0, but has since been fixed in our TLF 2.0 open source.

When the mouse cursor is over text, if the text is editable or selectable, the mouse cursor will show as an I-beam. If the text is neither editable nor selectable (i.e., the textFlow's interactionManager is null), then the cursor doesn't change as it goes over the text, it will show as a simple arrow. This is by design to show that the text cannot be selected. When you switch from having a valid textFlow.interactionManager to one that is null, the cursor should be changed to an arrow.

You can check out our pre-release version on SourceForge, but assuming you need to use the release version of TLF, the best workaround is probably to reset the mouse cursor directly, like this:

     Mouse.cursor = AUTO;

Thanks,

- robin

1 reply

R
Adobe Employee
robin_briggsCorrect answer
Adobe Employee
August 2, 2010

This sounds like a bug that was in TLF 1.0, but has since been fixed in our TLF 2.0 open source.

When the mouse cursor is over text, if the text is editable or selectable, the mouse cursor will show as an I-beam. If the text is neither editable nor selectable (i.e., the textFlow's interactionManager is null), then the cursor doesn't change as it goes over the text, it will show as a simple arrow. This is by design to show that the text cannot be selected. When you switch from having a valid textFlow.interactionManager to one that is null, the cursor should be changed to an arrow.

You can check out our pre-release version on SourceForge, but assuming you need to use the release version of TLF, the best workaround is probably to reset the mouse cursor directly, like this:

     Mouse.cursor = AUTO;

Thanks,

- robin

S
sunny_chandelAuthor
Known Participant
August 3, 2010

So when this TLF 2.0 be available to use.

R
Adobe Employee
robin_briggs
Adobe Employee
August 3, 2010

It's available now in prerelease. We don't have a date yet for when its final.

- robin

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices