View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000142 | Ecere SDK | ecere | public | 2008-09-18 19:35 | 2012-04-17 02:09 |
Reporter | jerome | Assigned To | |||
Priority | high | Severity | major | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Target Version | 0.45 Ginkakuji | ||||
Summary | 0000142: Refine DataBox control | ||||
Description | 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. | ||||
Tags | No tags attached. | ||||
|
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 |
Date Modified | Username | Field | Change |
---|---|---|---|
2008-09-18 19:35 | jerome | New Issue | |
2009-05-03 05:45 | jerome | Description Updated | |
2012-03-08 16:52 | redj | Target Version | => 0.45 Ginkakuji |
2012-03-29 07:53 | redj | Category | => Ecere Runtime Library |
2012-03-29 07:53 | redj | Project | @1@ => Ecere SDK |
2012-04-17 02:09 | jerome | Note Added: 0000591 | |
2012-04-17 02:46 | jerome | Note Edited: 0000591 |