You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1600436296 <uvos> Wizzup: you can see the number then, but you cant see it as you type
1600436302 <Wizzup> ok
1600436325 <uvos> Wizzup: dont have beta installed
1600436331 <uvos> Wizzup: ill try nokia nseries
1600436335 <uvos> Wizzup: the default theme
1600436342 <Wizzup> uvos: no need
1600436347 <uvos> ?
1600436348 <Wizzup> I do see some text, I just see it delayed
1600436353 <Wizzup> like, press 2+2
1600436357 <Wizzup> then I will see '2+'
1600436361 <Wizzup> but not the last
1600436364 <Wizzup> and then '=' makes all visible
1600436371 <uvos> Wizzup:
1600436376 <uvos> i can highlight the text
1600436378 <uvos> its there
1600436380 <uvos> its just black
1600436381 <Wizzup> I'm pretty sure this is just a style problem
1600436420 <Wizzup> I'm trying libpurple-slack with haze, but haze seems to throw sigtrap
1600436454 <uvos> Wizzup: type 9s untill the keypad disables itself
1600436489 <Wizzup> uh what?
1600436498 <uvos> and then drag your finger over area to the right of the back button
1600436514 <uvos> in osso_calculator
1600436528 <Wizzup> it is visible, just black on dark grey
1600436548 <Wizzup> (clearly a style problem)
1600436555 <Wizzup> well that's probably marina related
1600436556 <uvos> Wizzup: its not a style problem
1600436558 <Wizzup> I use beta
1600436570 <uvos> Wizzup: its because it uses the wrong color field
1600436579 <Wizzup> I'm telling you it is a style problem
1600436581 <uvos> Wizzup: it needs to use window text qt color field
1600436585 <uvos> Wizzup: no its an app problem
1600436587 <Wizzup> all qt5 apps with maemo style have problems rendering text fields
1600436590 <Wizzup> and they all do it wrong
1600436604 <Wizzup> try countdowntimer settings
1600436610 <uvos> Wizzup: its using the content text color field
1600436622 <uvos> Wizzup: thats wrong because its set against the window color
1600436625 <uvos> not the content colr
1600436627 <Wizzup> open 'settings' in countdowntimer
1600436635 <Wizzup> and relaise that both these apps are unchanged colour wise from fremantle
1600436640 <Wizzup> and in fremantle and renders fine
1600436644 <Wizzup> this is a style problem
1600436717 <uvos> Wizzup: the spec changed between qt4 and qt5
1600436722 <uvos> to allow themes like this:
1600436830 <uvos> http://uvos.xyz/scr.png
1600436911 <uvos> previously the window color and the content text color where defined to have high contrast
1600436920 <uvos> this is why it works on fremantle
1600436929 <uvos> this is now out of spec
1600437084 <Wizzup> hm
1600437161 <uvos> Wizzup: so we can change our themes to make it work, but the applcations are out of spec by assuming that those 2 colors have high contrast
1600437268 <Wizzup> we can at least pick a better colour I guess
1600437335 <uvos> Wizzup: right
1600437354 <uvos> Wizzup: this is a problem i have been fihgting lots since i use sutch an unusal theme on my desktop
1600437356 <uvos> :P
1600437387 <uvos> there where many applcations that violated this in the past
1600437393 <uvos> i has become mutch better now to
1600437395 <uvos> *tho
The text was updated successfully, but these errors were encountered:
IMbackK
changed the title
Qt maemo widgets use window color as background but then use base text color and vice versa
Qt maemo widget themes use window color as background but then use base text color and vice versa
Jan 16, 2023
see https://doc.qt.io/qt-5/qpalette.html
The text was updated successfully, but these errors were encountered: