RT#6999: Bug: Comment "text indicator/note" icon behaviour inconsistent SOLVED

[rakunavi]

=== UPDATE ===================================================================
The issue reported below has been resolved in Ver 10.7.3 build 401.
I appreciate all the hard work and efforts of the support and development team.
==============================================================================

Hello all,

I understand that when some text is entered in the pop-up note, a Text Indicator icon is displayed beside the comment, as long as the "Show Text Indicators" option is enabled in the preferences.

• figure.png

Based on this understanding, the following two behaviors seem a bit odd.

1. The text indicator does not appear after the measurements are cleared.
2. The text indicator does not appear after changing a polyline, etc., where the text is entered in the pop-up note, to a line, etc.

In both cases, the text indicator appears when displayed in Acrobat.

Below is a detailed look at each case.

(1) The text indicator does not appear after the measurements are cleared.

• When I clear the measurements for the Distance Tool, the Perimeter Tool, and the Area Tool, the values still remain in the pop-up note (*), but the text indicator is not displayed (**). Assuming my understanding at the beginning, it would seem that the text indicator should be displayed.
  
  I am also concerned about the inability to edit or delete the remaining values in the pop-up note after "Clear Measurement" is executed. If the measurement line is cleared, it should be the same as a normal line comment, and I should be able to edit the values entered in the pop-up note, but I can't edit anything, as if it is locked.
  
  
  • Animation1.gif
  However, on the other hand, if a line, polyline, or polygon where text is entered in the pop-up note is converted to a measurement, the pop-up note will contain the "pre-registered text + measurement value". When the measurement is cleared, the measurement value is deleted from the pop-up note and only the original "pre-registered text" remains. Of course, the text indicator is also displayed. This behavior alone could be interpreted to mean that the "Clear Measurement" command includes deleting the measurement values from the pop-up note. If this is the developer's intention, then the fact that the values remain in (*) itself does not reflect the developer's intention, and the fact that the text indicator is not displayed in (**) may be the developer's intention.
  
  
  • Animation2.gif

(2) The text indicator does not appear after changing a polyline, etc., where the text is entered in the pop-up note, to a line, etc.

• When a comment where the text is entered in the pop-up note is changed, as in the following combination, the text is carried over to the pop-up note of the comment after the change, but the text indicator is not displayed.
  
  
  • When a polyline is changed to a line
  • When a polyline is changed to a polygon
  • When a polygon is changed to a line
  • When a polygon is changed to a polyline
  • When a rectangle is changed to a line
  • When a rectangle is changed to a polyline
  • When a rectangle is changed to a polygon
  
  
  • Animation3.gif

I can't say what reflects the developer's intent or what is correct as ISO 32000-1:2008 specification, but from my understanding as I wrote at the beginning, the two points I mentioned above seem somewhat odd.

Hoping that the above information will be of some help to you.
Thank you so much for your continued support.

Best regards,
rakunavi

- PDF-XChange Editor Plus Version: 10.3.1 build 387
- OS Version: Windows 11 Home 23H2 Build 22631.3737
- PC Model: Lenovo IdeaPad C340-15IWL, HP All-in-One 22-c0xx

[Daniel - PDF-XChange]

Hello, rakunavi

Thank you for the report, I have reproduced this and created a ticket on it for you:

RT#6999: Bug: Comment "text indicator/note" icon behaviour inconsistent.

Kind regards,

[rakunavi]

Thank you, Daniel, for creating the ticket!

I am relieved to share my situation with you.
Thank you for taking time out of your busy schedule.
Please give my best regards to developers.

Best regards,
rakunavi

[Daniel - PDF-XChange]

[rakunavi]

Hello PDF-XChange Support,

The report at the beginning of the topic consisted of two issues.

1. After executing the “Clear Measurement” command, the text indicator does not reflect the actual status of the pop-up note.
2. After applying the “Clear Measurement” command to annotations created with the measurement tool, the comment pop-up notes cannot be edited.

Regarding the first issue, as described in the version history below, it was already improved in build 388.

• PDF-XChange Editor Version History - Build 10.4.0.388
  Fixed some inconsistencies with the text indicator icon for comments. (T# 6999) (43038)

However, the second issue persists as of build 400. Due to the change in build 388, values are no longer transferred to the pop-up note when applying the “Clear Measurement” command. Therefore, while some descriptions does not match the current state, the remaining ones still apply to build 400 as is.

I am also concerned about the inability to edit or delete the remaining values in the pop-up note after "Clear Measurement" is executed. If the measurement line is cleared, it should be the same as a normal line comment, and I should be able to edit the values entered in the pop-up note, but I can't edit anything, as if it is locked.

Regarding the issue where pop-up notes become uneditable—as if locked—after using the “Clear Measurement” command, may I ask about the current status of its handling? If it’s still in the queue, that’s perfectly fine. I just wanted to check in, as I was a bit concerned it might have been overlooked.

• Video.webm

Best regards,
rakunavi

- PDF-XChange Editor PRO Version: 10.7.2 build 400
- OS Version: Windows 11 Pro / Home 24H2 Build 26100.6584
- PC Model: GMKtec Nucbox M7 Pro with HUION Kamvas Pro 19 / Lenovo IdeaPad C340-15IWL

[Dimitar - PDF-XChange]

Hello Rakunavi,

I’ve asked our developers to review this ticket again and check whether the issue is still present.

We’ll get back to you as soon as they respond.

UPDATE: Our developers told me that this problem is fixed in today's build.


Best regards,

[rakunavi]

Hello Dimitar, thank you for contacting the developers.

I also appreciate you letting me know that the issue has been addressed in the build 401 update.
It's great that I was able to share the additional report at just the right time. I truly appreciate everyone's efforts.

Best regards,
rakunavi

[Dimitar - PDF-XChange]