My personal wishlist right now is only to fix the bug that causes TheIDE to occasionally erase the entire undo history and go back to the top of an edited document when building a program. It sometimes happens 10-15 times during a session now. It's making me want to use a separate editor since I can't confidently test new changes to a program without worrying that they'll become permanent because a bug kills the undo buffer.

Very well done Mirek.

My personal wishlist right now is only to fix the bug that causes TheIDE to occasionally erase the entire undo history and go back to the top of an edited document when building a program. It sometimes happens 10-15 times during a session now. It's making me want to use a separate editor since I can't confidently test new changes to a program without worrying that they'll become permanent because a bug kills the undo buffer.

Hello jjacksonRIAB,

jjacksonRIAB wrote on Thu, 31 August 2023 20:22

Very well done Mirek.

My personal wishlist right now is only to fix the bug that causes TheIDE to occasionally erase the entire undo history and go back to the top of an edited document when building a program. It sometimes happens 10-15 times during a session now. It's making me want to use a separate editor since I can't confidently test new changes to a program without worrying that they'll become permanent because a bug kills the undo buffer.

The occasional undo history overwrites was fixed by this commit. It fixes the issue when you open licenses and statistics dialog. This will be the part of the next release. If you can provide reproduction scenario we will be grateful. You can also look for "ClearClipboard()" and "AppendClipboard()" usage within U++ code base and especially TheIDE (ide packages) and tell us if you are using one of options that are calling this function.

-------
Mirek good work on the next release. It should be 2023.2 not 2023.1.

Klugier

Very well done Mirek.

My personal wishlist right now is only to fix the bug that causes TheIDE to occasionally erase the entire undo history and go back to the top of an edited document when building a program. It sometimes happens 10-15 times during a session now. It's making me want to use a separate editor since I can't confidently test new changes to a program without worrying that they'll become permanent because a bug kills the undo buffer.

Mirek,

It happens to me in Linux Mint, Arch Linux and FreeBSD with two different computers, three different filesystems (ext4, ext3, zfs). I don't use Windows much anymore so I cannot confirm its existence there. I don't see what I could be doing different, I just press build and after the build is done boom - edit window refreshes, latest changes disappear, undo/redo buffer is erased, cursor is moved to the top of the document. This happens with both clang and gcc. I cannot reproduce it on fresh projects, it appears to manifest on larger projects particularly after theIDE has been open for a while and when quick changes to a document have been made in succession.

It's as if theIDE is losing sync with the files/timestamps on disk, letting you continue working on an unsynced ghost copy of the file and then reloading the last saved version during build but I cannot be entirely sure what's going on, being unable to reliably reproduce it. I don't know if any of this information helps.

I kind of wonder whether the autosave routine is failing to flush to disk or losing track of the handles and timestamps it is observing.

Is this a new problem with current master or was it doing that in say 2022 versions too? (There is a new logic intended to add unco records when files changes outside of theide which could be related, but it is just in master, since ~ 6/2023).

Do you edit files after starting the build?

To what point files revert?

- New C++ sources indexer mode - previoualy, after each file change, all depended files were reindexed. That often resulted in very heavy CPU load after each header change. In the new mode, only the changed file is being reindexed - while less accurate, real problems in this new mode are actually rare and it makes for much more responsive experience using theide.

...this is somehow an extension to this post.

Quote:

- New C++ sources indexer mode - previoualy, after each file change, all depended files were reindexed. That often resulted in very heavy CPU load after each header change. In the new mode, only the changed file is being reindexed - while less accurate, real problems in this new mode are actually rare and it makes for much more responsive experience using theide.

I think i see your point here, altough the thing is far from perfect(checked both included clang on w7 and msbt17 and no go).
But i think you forgot to see both point of view:
* from developing upp point of view it's probably better(since new mode recompiles "needed" - mostly developing "system" header sources faster),
* from consumer point of view(just using the ide out of the box for a quick project) - original is magic - it works!

With this i incline that original and new modes of indexer should be selectable in Settings,

original mode is a must for people who want: "do it's thing at opening project and then just use it",

I think I have found possible culprit, I mean error that is quite consistent with what we see:

https://github.com/ultimatepp/ultimatepp/commit/b16e199ae61a 3290d5e4cb53206d502eb98c4700

Please recompile theide and check...

Mirek

Now I am not sure whether whether you are speaking about pre-libclang homegrown parser or about difference between 2023.1 and 2023.2.