Skip to main content
J
jstern1-Visitor
1-Visitor
March 26, 2015
Question

Why does Selecting elements not stick in Arbortext editor 6.0 (occasionally)?

  • March 26, 2015
  • 1 reply
  • 2047 views

Has anyone else experienced an intermittent problem where select does not stick.

For example, I select a word and then press ENTER to markup the selected text. By the time I select the markup to wrap the selected text, the text is no longer selected. There are no error messages in the bottom of the Arbortext Editor screen.

This also happens when I want to select text to delete. Before I can hit the delete key, the text has become unselected. I have even tried right-clicking and using the Select Element Content or Select Element options, but the same thing happens...the item is selected but for a second and then the selection disappears.

Just wondering if this ever happens to anyone else and how to get rid of this annoying problem.

    1 reply

    R
    rdiaz5-Regular Member
    5-Regular Member
    April 2, 2015

    Hi Janet,

    I haven't heard of an issue like this happening any time recently. A couple of things to check:

    What version of Editor are you using (6.0 M?)?

    What OS are you using?

    What customizations are you using?

    If you have any scripts that scan the document for changes, or react to cursor placement, I could see them having an impact, but it really depends on the coding.

    J
    jstern1-VisitorAuthor
    1-Visitor
    December 9, 2015

    My company is fairly new to using Arbortext Editor and we don't have scripts attached to the editor yet. This is happening to a few people. Basically, after awhile, Arbortext Editor will let you select text or an element, but after one second it forgets about the selection. We are using Arbortext Editor 6.0M running on Windows 7. We do have a few customizations, but they are utilities you click on to activate.

    Also, we are using Arbortext Editor with SDL LiveContent Architect.

    R
    rdiaz5-Regular Member
    5-Regular Member
    January 21, 2016

    Hey Janet,

    Unfortunately, I'm not familiar with SDL LiveContentArchitect.

    If it, or your scripts, use some form of heartbeat monitor or such to check for changes, I could see this happening.  The Core product doesn't seem to have displayed this issue, however, which is why I'm leaning more towards the add-ons.

    If you could open a case with TS, we could at least confirm if this is the case, and if so, perhaps provide a best practice to prevent it from happening.

    If it ends up not being related to the scripts, we may find something else.

    Please note, however, 6.0 and lower are on sustained support, which mean bug fixes are no longer provided for them.

    Thanks!

    Terms & ConditionsCookie settingsAccessibility statement