Copy link to clipboard
Copied
Dear all,
Since quite a number of FM version the Marker Pod shows the selected marker only if it is open, before t he marker symbol is selected. This makers it impossible to get the marker text visible in the pod for the setting "Auto-collapse Iconic Panels" (FRMAKER-10962 ). Please vote on this!
Test
- Have a marker symbol selected in the document
- Open the Marker Pod
→ Nothing is displayed
- Going back to the document closes the Marker pod according to the settings
- Place cursor behind the marker symbol
- Open the Marker Pod
The following allows to see the marker contents, if the mentioned setting is OFF):
- In the document select the marker symbol
→ If the setting is ON, this operation immediately closes the Marker Pod...
Workaround
Do not use "Auto-collapse Iconic Panels" = ON for certain work. This is clumsy, as the setting is welcome in most cases.
Klaus, thank you very much!
Yes. Very annoying. I voted for your tracker report.
(Your link is not correct. This is the correct link: https://tracker.adobe.com/#/view/FRMAKER-10962)
There are already a few other reports about this. I will mention these in the comments of the report.
Please also consider this marker issue:
https://tracker.adobe.com/#/view/FRMAKER-10620
In the marker pod I cannot use any shortcut to create or change a new marker. I enter the text, e.g. for an index marker, and t
...Copy link to clipboard
Copied
Klaus, thank you very much!
Yes. Very annoying. I voted for your tracker report.
(Your link is not correct. This is the correct link: https://tracker.adobe.com/#/view/FRMAKER-10962)
There are already a few other reports about this. I will mention these in the comments of the report.
Please also consider this marker issue:
https://tracker.adobe.com/#/view/FRMAKER-10620
In the marker pod I cannot use any shortcut to create or change a new marker. I enter the text, e.g. for an index marker, and then I have to switch to the mouse to accept my changes. Not convenient!
Copy link to clipboard
Copied
Thanks for your comments and regencies to the bug which obviously was introduced with FM-14 (2017)