I have noticed (since 4.11) that after I add a comment to a node (or a bubble) I will continue working
in the BP but when I go back to a note the comment is gone - it has been reset back to the default [Click to edit].
I’ve been trying to reproduce the issue but it is very random that I can’t (yet) find a pattern.
It isn’t a show stopper, just a little irritating to keep retyping some important comment.
The obvious workaround is to keep going back to any edits intermittently as you work to see if it is still there.
If not you can retype it before you forget what you wrote.
Does this occur in a clean, blank project with no additional content or is it limited to one project?
When you type in the comment, what are the exact steps you are taking? For instance, are you pressing enter when ending the comment or do you click away from it?
“Does this occur in a clean, blank project with no additional content or is it limited to one project?”
It seems to be limited to my main project so far, the one project that has been evolving over time (since 4.8). I rarely work with clean blank projects so can’t say if that makes a difference yet. I’ll have to do some tests.
“When you type in the comment, what are the exact steps you are taking? For instance, are you pressing enter when ending the comment or do you click away from it?”
(1)Activate the edit box (2)Enter some text (3)Press enter to close the edit box.
I know the text is not accepted if you don’t press ENTER as the comment reverts back to [Click to edit] immediately. That is not the issue here as I always glance back (out of paranoia) after entering text.
Unfortunately it can be several minutes after I continue to work then go back to
a particular BP only to find the text has reverted back to [Click to edit] even though I know 100% it was there.
I know that isn’t much help so I will try to record it live and see if I can get a repro. When I do I’ll post a link to the vid.
OK,
I made a concerted effort to track down the issue and I can now reproduce it.
(I knew I wasn’t going
It may not even be considered a bug but it is ‘kinda-a-bug’ because the UI gives the impression that everything is ok until you close/reopen your blueprint.
REPRO (4.12.3):
(1)
Open any blueprint (class or level)
(2)
Add any two nodes
(3)
In NODE-A add the comment “press enter to keep text”
(4)
Press enter to accept the text.
(5)
In NODE-B add the comment “click background to lose text”
(6)
Click the graph background to (falsely) accept text. The text looks fine, as if it has been accepted!
(7)
Save the blueprint and close it.
Now, at this point you think you have two saved text comments in your BP.
However, if you re-open the blueprint only [NODE-A] has the text you entered. The text entered into [NODE-B] has been reset back to “Click to edit”.
In every text editing software I can recall using, clicking away from an edit box (to lose focus) also acts as a command to keep the text. This is preferable UI design because deleting text you don’t need is much easier that recalling/retyping lost text all over again, possibly from several minutes ago.
It is ‘kinda-a-bug’ because if it was mandatory for ENTER and ONLY ENTER to be pressed to retain a comment then the text should reset back to “Click to edit” ‘as soon as you click the background’.
As it stands, it appears that your text is safe until you close and reopen the blueprint only to find that the comment has been trashed.
I have tested this on my end and when I LMB away from the comment it does not create a comment, so I believe this is the intended functionality. Try verifying your engine build by going to the Launcher>Library>Dropdown context menu (4.11)>verify. This should check to ensure there are no missing/damaged files in your 4.11 build and repair/replace them as necessary.
“when I LMB away from the comment it does not create a comment”
That’s strange because I can’t recall ever seeing that behaviour which is why it was so apparent to me.
I did the launcher-library verify you suggested (of my 4.11.2 and 4.12.3) but it made no difference in either build. I can reproduce the issue every single time now that I have know the repro steps.
(I only started noticing this issue in 4.11).
Here’s a video showing the comment being lost in 4.12.3:
Ah, I misunderstood previously and was attempting to enter the node comment through the RMB context node. I was able to reproduce this on my end and have entered a bug report, UE-32535, to be assessed by the development staff.
For the record this is really frustrating… Must’ve lots hundreds of comment edits this way so far…
If you edit a comment and click away from it, it’s fine, the edit is there. But if you compile the blueprint or duplicate a node somewhere then the comment reverts back to what is was… so it’s not something you notice until you go back to read your comments.
In the mean time I did come across a workaround in the forums somewhere - that is to make sure you press ENTER after editing the comment (instead of just clicking away). That seems to commit it properly and it stays there.
