#pyqt | Logs for 2019-03-03

Back
[00:00:01] <Avaris> yeah, noticed :)
[00:00:39] <Avaris> if you don't multiply you'll paint over. this is normal :)
[00:02:01] <altendky> right. but the fact that one piece is opaque and the other translucent suggests to me that at least it isn't meant to be in front entirely
[00:02:15] <altendky> but perhaps the focus (the translucent one) is
[00:02:55] <altendky> i'm guessing that if it were drawing text as well it would put the text in front of the selected paint at least. possibly in front of the focus paint as well
[00:02:57] <Avaris> one is full background paint, the other border (rect)
[00:03:14] <altendky> i get a translucent gradient for the focus
[00:04:00] <altendky> https://usercontent.irccloud-cdn.com
[00:04:35] <Avaris> mine is just a dotter border
[00:04:53] <altendky> do my comments make a bit more sense now? :]
[00:05:42] <altendky> i think the situation here is that the widget isn't a sensible one for use with the highlights
[00:05:55] <altendky> the widget should generally show the background through
[00:06:17] <Avaris> make widgets define their own highlight/select :P
[00:06:26] <altendky> optionally, yes
[00:06:40] <altendky> i added the draw_* parameters already
[00:06:52] <Avaris> what does multiply do with that gradient?
[00:06:55] <altendky> the other half is to pass the `option` or some portion of it to the widget fill
[00:08:03] <altendky> makes it just shy of invisible
[00:08:20] <Avaris> no, i mean, make 'render' return full thing based on selected etc
[00:09:26] <altendky> yes. the dev could do that with draw_standard_item=False to prepare() and then i would have to pass them the option (or a portion of it) to the filler function so they could decide how to respond to whatever state they wanted (selected/focus for what we are discussing now)
[00:09:40] <altendky> but there's plenty more in there that could be appropriate for the widget to know about
[00:14:00] <altendky> i don't think either the focus or select should be changing foreground text in the widget. so i think the 'control' should be rendered first without any multiply applied to anything. if the dev doesn't want that done, they can already disable it. if they want to have the widget respond, i need to pass them more info.
[00:15:22] <altendky> presumably the left column looks 'as expected' when the control is drawn first
[00:16:33] <Avaris> sure but then you need your widgets to have full transparent background, which isn't intuitive (hence the stylesheet on textbrowser)
[00:17:08] <altendky> i think that's a thing to document. "if you want to look 'normal' then consider that normal items don't draw their own background"
[00:17:20] <altendky> back that with an example or whatever
[00:17:45] <altendky> and stylesheet might not be required. QWidget has a related thing.
[00:18:17] <altendky> i'm trying to make it easy to use properly, not make a thing that when used improperly looks wrong but not as wrong as it could be.
[00:19:18] <Avaris> (btw that half transparent background wasn't working for me. so i got no selection colors there)
[00:19:28] <altendky> hmm...
[00:19:38] <Avaris> might be a windows thing
[00:19:50] <altendky> might be easier to debug with a pattern or such in the background
[00:20:07] <altendky> you can see overlaps but don't depend on translucency
[00:22:29] <altendky> Consider that the 'inspiration' for this had a background on the list view so presumably they have translucent backgrounded 'items'
[00:24:29] <altendky> Though they may want any highlight shown in the text bubble. Either way, I don't think they would want anything overlayed over the text.
[00:29:46] <altendky> The stack order could easily be configurable, just in case
[00:31:24] <Avaris> sure. multiply/overlay was kinda hack anyway
[01:10:53] <altendky> Avaris: thanks again for all the help.
[01:40:42] -!- kallesbar has joined #pyqt
[04:14:22] -!- storgance has quit [Quit: Connection closed for inactivity]
[04:34:14] -!- kallesbar has quit [Ping timeout: 255 seconds]
[04:45:11] -!- kallesbar_ has joined #pyqt
[05:21:52] -!- BPL has joined #pyqt
[06:53:21] -!- mintograde has joined #pyqt
[07:15:27] -!- kallesbar_ has quit [Ping timeout: 245 seconds]
[10:44:20] -!- mandeep has joined #pyqt
[11:18:22] -!- kallesbar_ has joined #pyqt
[11:28:11] -!- kallesbar has joined #pyqt
[11:32:20] -!- kallesbar_ has quit [Ping timeout: 250 seconds]
[14:04:36] -!- mandeep has quit [Remote host closed the connection]
[14:14:12] -!- storgance has joined #pyqt
[14:45:01] -!- kallesbar has quit [Quit: Konversation terminated!]
[18:49:49] -!- BPL has quit [Quit: Leaving]
[19:10:23] -!- JanC has quit [Ping timeout: 258 seconds]
[19:39:11] -!- JanC has joined #pyqt
[22:00:08] -!- JanC has quit [Remote host closed the connection]
[22:00:25] -!- JanC has joined #pyqt
[22:50:56] -!- mintograde has quit [Ping timeout: 268 seconds]