hum, there is still a case where I really cannot imagine when there is a
first action in a transaction: when Scintilla decide to not coalesce
simple
typing actions, in this case, I do not call BeginUndoAction but I must
know
that a new transaction started (in fact nobody calls BeginUndoAction in
this
case). And without such a limit I cannot count anything :(
If there is no coalescing then you should see two SC_START_ACTIONs.
OK cool, so let's (try to) summarize what we told:
- having a separate notification for SC_START_ACTION is not necessary.
Rather than this the SC_START_ACTION should/can be melt into the first true
action that happens for a transaction
- BeginUndoAction must break coalescing (what it already does, no?)
It means that:
- BeginUndoAction code should remain as earlier code
- I must find a way to detect during the InsertString/DeleteChar stuff that
the action is the first one of a transaction (either because at top level
and not coalesced or inside a transaction and the first), and send
appropriately the SC_START_ACTION notification flag in the action
notification
- the SC_START_ACTION flag is sent only for non-undo/redo actions
OK?
Regards
Armel
_______________________________________________
Scintilla-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scintilla-interest
