Using Cut command with no selection crashes TCoolEdit
Borland's Object Windows Library for the modern age
Brought to you by:
jogybl,
sebas_ledesma
Pushed a fix in [r5756]
Some notes:
Related
Commit: [r5756]
Good catch!
Not that I see. It is an internal issue and the fix does not affect the ABI. Since the crash is easy to reproduce, and the severity is high (loss of data), I think it warrants a fix in 6.44 and 7.0, even though CoolPrj probably has few users.
So, feel free to set the milestone to 6.44, and I will merge your fix when we approach the next release (unless you want to rekindle your role as release manager, in which case you can go ahead and merge and release immediately, if you want — see "Preparing and releasing a new version" for the steps needed).
PS. Agree on all your other notes, by the way, although the API changes should be limited to 7.1, in my view.
Hi Jogy, I just recompiled OWLMaker with your fix, and issuing the Cut command with no selection now does not crash, which is good, but I spotted another issue: Undoing a Cut command causes a CHECK assertion in TUndoDeleteSelection::Undo. If ignoring it, the program seems to run fine. However, if I make a series of edits and cuts and then issue Undo repeatedly (ignoring the assertions) the text isn't properly restored.
PS. I see that TCoolEdit has Redo functionality, but this is not on the menu in OWLMaker, nor in your test example.
Yeah, that is another issue - we should look to fix it.
Also I added the Redo command to the menu, but it does not get enabled and does not work.
Added [bugs:#528] to address the CHECK assertion and working on it.
Related
Bugs:
#528Last edit: Vidar Hasfjord 2022-02-19
As it looks, there may be a bunch of other issues as well - we should merge all non-API changing fixes back to the old branches.