MantisBT - Ecere SDK
View Issue Details
0000142Ecere SDKecerepublic2008-09-18 19:352012-04-17 02:09
jerome 
 
highmajorhave not tried
newopen 
 
0.45 Ginkakuji 
0000142: Refine DataBox control
The DataBox control is available from the toolbox as a common control, yet it is mainly targeted as the core functionality of the ListBox at the moment.

Improve its usability as a general control.


Its integration with EDA / SavingDataBox etc.
No tags attached.
Issue History
2008-09-18 19:35jeromeNew Issue
2009-05-03 05:45jeromeDescription Updated
2010-07-25 22:29redjRelationship addedchild of 0000430
2010-07-29 15:34jeromeRelationship deletedchild of 0000430
2010-07-29 15:34jeromeRelationship addedchild of 0000431
2012-03-08 16:52redjTarget Version => 0.45 Ginkakuji
2012-03-08 21:21redjRelationship deletedchild of 0000431
2012-03-29 07:53redjCategory => Ecere Runtime Library
2012-03-29 07:53redjProject@1@ => Ecere SDK
2012-04-17 02:09jeromeNote Added: 0000591
2012-04-17 02:46jeromeNote Edited: 0000591

Notes
(0000591)
jerome   
2012-04-17 02:09   
(edited on: 2012-04-17 02:46)
NotifyModified vs NotifyChanged
The names are confusing at best.

Generally, the one you want to use is NotifyChanged.

When to use NotifyModified?

I think NotifyModified is for EditBox'ish editing, where things update every time a character is added, but the definitive result is not known yet, vs drop box style editing which might not bother calling NotifyModified.

There are some locations where it's used in EDA:

- idList.ec: The StringList implements both methods, and there is only a slight variation where the 'NotifyChanged' version does not scroll the listbox. Should NotifyModified be updated with this code as well? Is NotifyModified needed at all in this case