BUG: Annotation loses label when moved from one note file to another note file (Win 6.0a Beta 2 6.0.

Tim Hensler · 2014-11-16T20:43:00+00:00

Repeatable problem: * Mark a text in NASB with a highlight style that has a label * Check the annotation in note file A to confirm it has a label * Hover over the text in NASB to confirm it has a label associated with it * Move the annotation from note file A to note file B * Check annotation in note FIle B - it does not…

Tim Hensler

Repeatable problem:

Mark a text in NASB with a highlight style that has a label
Check the annotation in note file A to confirm it has a label
Hover over the text in NASB to confirm it has a label associated with it
Move the annotation from note file A to note file B
Check annotation in note FIle B - it does not have a label
Hover over the text in NASB - it no longer has a label associated with it
Make sure note file A has focus
Press Ctrl-Z to undo the move (puts annotation back to note file A and leaves the copy in note file
Check both annotations and find neither has the label associted with them
Hover over the text in NASB - it too still does not have a label associated with it
Make sure note file B has focus
Press Ctrl-Z to undo the move (removes the annotation from note file
Check the annotation in note file A - no label
Hover over the text in NASB - no label

Find more posts tagged with

Comments

Bradley Grainger (Logos)

I've reported this bug also.

Dylan Rondeau

This should be fixed in 6.0b Beta 2.

Tim Hensler

This does NOT work correctly. When I do step 4, the text in NASB looses both the label and the highlight formatting, but the note in note file B still has the label associated with it. When I undo the move (putting the note back into note file A), the text in NASB regains both the label and the highlight formatting.

Dylan Rondeau

This does NOT work correctly. When I do step 4, the text in NASB looses both the label and the highlight formatting, but the note in note file B still has the label associated with it. When I undo the move (putting the note back into note file A), the text in NASB regains both the label and the highlight formatting.

What I verified was fixed was that the label wasn't lost when moving from note A to note B. I'll reactivate/make a new case for the moved highlight not appearing in the resource - sorry for that.

Interestingly, after pressing Ctrl+Z to replace the annotation in note A and leaving the copy in note B, you can delete the annotation from note A and the highlight/label will remain in the NASB (the desired behavior). I'm not sure why that is.

Seth Copeland

This does NOT work correctly. When I do step 4, the text in NASB looses both the label and the highlight formatting, but the note in note file B still has the label associated with it. When I undo the move (putting the note back into note file A), the text in NASB regains both the label and the highlight formatting.

In my test, the highlight/label is not truly lost, but the resource display was refreshed to indicate the note was removed from the one document, but not refreshed to indicate it had been added to the other.

When I close and reopen the resource, the highlight and label both appear to still be intact.
Can you verify the same behavior?

-Seth Copeland

Tim Hensler

Thank you, Dylan.

Yes, there is some strange behavior going on. After I moved the note to file B and then did Ctrl+Z (so the note was in both files) I noticed the text in the resource was tagged twice (overlapping one another). When I deleted the note in file B, then there was one tag on the resource text. I didn't have time to test and document all the combinations (sorry) but am glad you were able to reproduce the problem.

Tim Hensler

Can you verify the same behavior?

Hi Seth,

I may not be able to retest until tonight or tomorrow night (sorry), but will test and report as soon as I can. Thank you for your help.

Seth Copeland

I may not be able to retest until tonight or tomorrow night (sorry), but will test and report as soon as I can. Thank you for your help.

I just pushed a fix that should make it into the next beta. Thanks a lot Tim for finding and reporting these issues! It is much appreciated.

-Seth Copeland