Version: 5.5.3
OS version: Win7 x86 Enterprise
Error reported: Actually I believe I found 2 bugs linked to each other.
Bug 1)
If you set a debug marker in one line and therafter decide to close some code blocks (I mean pressing the "-" in a line which starts with a new block ("{"))
then I am not able anymore to unmark that line. Moreover it seems that a different line gets marked instead. There seems to be an issue between the showed line of a line (which is right) and the line count of a file (which obviously is lower once you close a code block).
Bug 2)
Again, after using block closing feature I decided to undo things. That works. However if I then open some blocks again and play around with undo-redo feature then completly different lines get replaced/rewritten whats oh ever. After I realized what happened in my whole code (2000 lines in that file) it was corrupt. I could not know in which line what got undo/redo'ed... and played in a back up.
Ok what I thinks gets wrong here and causes both errors:
Undo/redo saves the line where the change made [I think it saves the line of the shown editor rather than the real line where the code is stored when all blocks are opened].
That is a critical error in my opinion and I would like to use this feature.
Oh a third thing:
you cannot search (neither search in file nor all-files-search) through code which is in a closed block. Don't know if this is a bug or a feature. If it is a feature I would be happy to turn it off in the options menue.
Thanks for reading and taking time. Don't hesitate to ask if you need more information / better description / an example. I know that my english is not perfect ;)
regards
exoooo
The first one has been fixed in the upcoming 5.6.3 release.
I'll look into problem two and three.
I performed some follow up tests. If you modify line 10 and then collapse three lines into one, then the undo and redo features will modify line 12, because this is the 10th visible line. However, redo also seems to be working incorrectly in other ways as well.
The problem can be reproduced with these steps:
Fault 1: Orwell Dev-C++ unexpectedly types "world" onto line 12
Although redo also seems to act on the wrong line in the same way, it's behavior is more erratic. I cannot determine a pattern to the incorrect behavior.
Fault 2: Instead of taking away the "world" written on line 12, the cursor moves over beyond world on line 12
Thank you for your work on this product. Let me know if I can provide additional information.
Last edit: David Harting 2014-09-12
I have rewritten code closing for version 5.8.4. This should fix all the mentioned bugs. Please keep me informed.