Hmm, okay, so the Appearance, not the Meta then? 2012.11.07. 15:20 keltezéssel, Martin Wittemann írta: > Hey, > I think we need to tweak the framework if you just want to change the font > theme. Otherwise, try to change the appearance theme as I wrote in the former > mail to see if my assumption is right. > Regards, > Martin > > > Am 07.11.2012 um 09:19 schrieb Henrik Pauli <[email protected]>: > >> This is the git master from yesterday :) I was surprised to see the >> same qx.theme.manager.* in 2.0.2's apidocs too, though. >> >> What are your thoughts about the fonts? For me, those would be the most >> important right now – and it's well possible I'm misusing the feature. >> >> On 11/07/2012 08:33 AM, Martin Wittemann wrote: >>> Hey, >>> the dynamic theme switch is a feature of the upcoming release. Do you use >>> the master of qooxdoo r a stable release? Because not changing background >>> colors sounds like you are not using the right version of qooxdoo. If you >>> do, we should check that bug and include it into the framework. :) >>> >>> Am 06.11.2012 um 18:21 schrieb Henrik Pauli <[email protected]>: >>> >>>> Well, I can seemingly easily switch between qx.theme.Classic and >>>> qx.theme.Modern (for example), but not my app's own theme. I created a >>>> timer that fires every second and changes some stuff while I'm testing, >>>> and during this, every 3 seconds it switches between themes: >>>> >>>> if ((counter / 3) % 2) { >>>> qx.theme.manager.Meta.getInstance().setTheme(qx.theme.Classic); >>>> } else { >>>> qx.theme.manager.Meta.getInstance().setTheme(qx.theme.Modern); >>>> } >>>> >>>> (It's probably worth mentioning that TabView tabs don't get redrawn >>>> until I hover them, and once returning to Modern, the tab background is >>>> taken from a system colour, unlike previously where it was white) >>>> >>>> If I replace those qx.theme.* with myapp.theme.Theme and >>>> myapp.theme.Theme2, where Theme and Theme2.js only differ in that they >>>> refer to Font.js and Font2.js respectively, and all theme files extend >>>> qx.theme.modern.Whatever, there will be no theme switching. There might >>>> be a too strict check somewhere in the code whether to switch or not... >>>> I'm not sure, I haven't looked yet. >>> It might be the case that it all depends on the appearance theme switch... >>> Could you just use another appearance class which simply extends the first >>> one and check that again? >>> >>> Regards, >>> Martin
------------------------------------------------------------------------------ LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
