strange behaviour with modify attribute dialog (Arbortext Editor 7.0)

[hbestler]

Hi,

if we would like to modfiy attributes of the markup, where the cursor is placed in, the Arbortext Editor shows the attributes of the wrong element.

You can see this in this example:

The cursor is inside the tag "para" but the modify attribute dialog shows the attribute dialog of the element "emphasis".

Our expectation is that the editor shows the attributes of "para", because the cursor is inside this element.

Can we change this behaviour? Maybe with a set-command? Or is this a bug of the arbortext editor?

Thank you for your help in advance.

Greetings from Germany.

[hbestler · Accepted solution]

Hi again,

it seems to be, that this behaviour is the expected behaviour for the PTC Arbortext Editor developers:

https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS121806

We cannot understand this.

Unfortunately it is not possible to change this.

[TimPhelps]

This is the content of the link sited. Knowledge Base article CS121806.

This functionality is in 5.3, 5.4, 6.0, 6.1 and 7.0 and probably before that.

• The previous element is recognized when using the
  modify attributes dialogue box.
• This is the behavior even when the previous element has
  closed.

<para>
  <indexterm>
   
<primary>Arbortext</primary>
  </indexterm>
 
<indexterm>
    <primary>courseware</primary>
 
</indexterm>With Arbortext, PTC University's faster and easier, using a
single source of learning content.(CLICK CURSOR
HERE)
</para>

• If the cursor was placed in the content above in the red area the expected
  element name in the modify attributes dialogue would be
  <para> as all the other elements have been closed.
• The actual behavior is that the modify attributes dialogue
  is the <indexterm> element.

[hbestler]

Meanwhile we found an own solution.

We noticed that the command 'oid_name(oid_caret())' returns us the current tag name where the cursor is inside.

The command 'current_tag_name()' returns the element at the left from the cursor.

So we could find an own workaround.