A cross-platform fetch doesn't sound closely tied to a particular UI toolkit. If not, it doesn't seem to belong in gio-x (nor gio core).
Editor.Modifiedshould be spelled
CanUndoin case we ever want the same for redo.
Elias Naur referenced this ticket in commit 24eb1a4.
I did some tests and I can adapt my application by replacing the underlying widget.Editor instance and keeping in memory only those widget.Editor that have been modified.
To do this, I still need undo and redo to be exported and also
- that Editor.SetText resets the modification history
- a new Editor.Modified function (or whatever name you prefer) that returns a bool indicating if the text has been modified. If the history is not exported, we need to be able to detect if the text is back to its initial state even if it has been modified and the modifications have all been undone.
~eliasnaur if you agree with this approach, I will modify the PR accordingly.
Thank you. Can you reproduce the issue using only core, such as
layout? By using
component.Gridthe bug is harder to debug
Why not just fill in reasonable
Names and let a future change align the other platforms?
Inkeliz referenced this ticket in commit b1dba5f.
Good question. It would be unfortunate to have platform-specific Names. Can you name examples of keys that don't have a natural name, or that is strictly platform-specific?
Thank you for the context.
Compared to replacing the underlying widget.Editor instance when switching between content, the use of the History field avoids to keep in memory the whole text and IME for all the modified texts (except for the one selected of course).
I see. It seems to me that History is a part fix for a general issue (that Editor don't work well with very large texts). It seems more natural to somehow abstract the underlying text storage so that the user can provide a storage method.