Sigh... OK, I've been digging into this a bit for the few last hours.
It's been a while but I (kind of ) start to remember things.
And the same problems and thoughts about it are back... :/
Apart from the "items" property not being stored and/or loaded etc. there are some other questions regarding "changable" lists:
- what happens if an element that has been selected is deleted from the list ?
- what happens if (on startup) a selected item is not in the item list ?
- does gDesklet has to look for multiple entries/values (or does the programmer has to?)
...
I remember spending a few hours (back then) on getting the list to be more flexible and finally putting it aside as more and more questions and problems popped up... :/.
Same thing today: the deeper I digged into it the more "ifs" and "whens" and problems showed up...
Anyway: do you really think we should keep on trying to have this fixed in 0.36.3 ?
Or shall we just keep it "non-editable" for 0.36.3 and try to implement this in 0.36.4 ?
Right now it seems to be working fine for pre-defined lists (AFAIK).
Sigh... OK, I've been digging into this a bit for the few last hours.
It's been a while but I (kind of ) start to remember things.
And the same problems and thoughts about it are back... :/
Apart from the "items" property not being stored and/or loaded etc. there are some other questions regarding "changable" lists:
- what happens if an element that has been selected is deleted from the list ?
- what happens if (on startup) a selected item is not in the item list ?
- does gDesklet has to look for multiple entries/values (or does the programmer has to?)
...
I remember spending a few hours (back then) on getting the list to be more flexible and finally putting it aside as more and more questions and problems popped up... :/.
Same thing today: the deeper I digged into it the more "ifs" and "whens" and problems showed up...
Anyway: do you really think we should keep on trying to have this fixed in 0.36.3 ?
Or shall we just keep it "non-editable" for 0.36.3 and try to implement this in 0.36.4 ?
Right now it seems to be working fine for pre-defined lists (AFAIK).