[EMAIL PROTECTED] schrieb: > Sebastian Werner <[EMAIL PROTECTED]> writes: > >> The problem is, to try to explain it a bit more, that each property can only >> store one value. As the appearance also does something like setColor >> internally it will overwrite the user values. We haven't already a good plan >> how to make this work better and keep the performance well, too. Any ideas >> for this are appreciated. >> >> This is also true, if you want to switch the appearance theme at runtime >> (which should be possible). This is also one reason, because we think we >> couldn't solve this just with changing the order or priority of the setter >> calls. > > If I'm understanding you correctly, it sounds as if currently, appearances are > applied multiple times, possibly even after the user has manually specified an > appearance attribute (e.g. setColor). What is the reason that general > appearance settings couldn't be applied only once, when a widget is created > (i.e. in the widget's constructor), so that manual changes simply override the > property setting that was initialized from the appearance upon widget > creation?
This is the case. It will be applied inside the constructor of QxWidget. But maybe you change the "enabled" property later and then the appearance overwrites your setting. Normally the easiest would be to handle both, a user and a appearance value. > > As to appearance theme changes at runtime, I think it's perfectly reasonable > that those completely override any manual settings that had been made. No not really. As appearance also controls some incompatible values. For example when you have a horizontalBoxLayout where: width = auto then the user configures width = null left = 0 right = 0 After this the appearance changes a reconfigure the width to width = auto This means, that a this moment the width, left and right properties are configured at the same time. And this is problematic. It would be better to also keep the user-configured null (or even undefined if we get implemented this). > If the > programmer wants to override settings after every appearance theme change, > it's reasonable that they would either modify the appearance theme itself, or > apply the manual settings each time the appearance theme is changed. Even better is to always handle user-configured stuff with a higher-priority, as then, there is no implicit change to properties which the user have already configured previously. For example I would like it if I change the appearance of a button, to "mybutton" and this redefines the width, where I have previously defined it to be statically to 100px. In my opinion this isn't intuitively understandable for the user. Sebastian > > Derrell ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
