[00:17] <ochosi> ali1234: oh, hmm, so it's all fine for you? strange. i guess i have to test whether the docker container makes any difference
[00:18] <ali1234> it seems to be
[00:18] <ochosi> i mean functionally autohide and intelli-hide work as they should
[00:18] <ochosi> it just seemed like there were unwanted flickers
[00:19] <ochosi> caused by too many signals that made the panel hide/show more often than needed
[00:19] <ali1234> its possible
[00:20] <ochosi> did you hover the mouse over the top 3px when opening the menu?
[00:20] <ali1234> no?
[00:20] <ochosi> cause then the mouse stays on the autohide-window and triggers another hide/show
[00:20] <ochosi> anyway, i'll try to write down clearer reproducing instructions tomorrow
[00:21] <ali1234> okay i see
[00:21] <ali1234> i can reproduce that - but it seems to be because the window open right under the mouse
[00:22] <ali1234> something like this
[00:22] <ali1234> 1. mouse enters autohide window, triggering unhide
[00:22] <ali1234> 2. panel appears
[00:23] <ali1234> 3. autohide window disappears - at this point the mouse leaves the autohide window because the autohide window moved, triggering a hide event
[00:23] <ali1234> 4. panel gets hidden
[00:23] <ali1234> 5. autohide window moved back under the mouse
[00:23] <ali1234> 6. mouse is now in the autohide window triggering unhide
[00:23] <ali1234> repeat...
[00:24] <ali1234> if i click on the menu and then close it without moving the mouse the panel appears and reappears 3 times
[00:25] <ali1234> but yeah, i'd look carefully at the mouse input events
[00:29] <ochosi> yeah
[00:29] <ochosi> just not sure how to solve that or why it worked in gtk2
[00:37] <ali1234> signal order changed probably
[00:37] <ali1234> i'd verify that input events get disabled on the autohide window as soon as its state changes
[00:37] <ali1234> and before its position changes
[02:58] <bluesabre> Seems like the lp build bots are stuck
[15:45] <subhadip> Hi. I am a developer and I want to make myself useful in the Xubuntu development. Although I have gone through the articles mentioned on the website, I would like if somebody present here could talk about it or give me a pointer to begin with. Thanks.
[16:31] <genii> subhadip: It's a slow week, but if you idle in here something will eventually happen :)
[16:35] <subhadip> genii: I hope so :)
[18:46] <Unit193> bluesabre: Part of the use of the upgrade tool is to remove packages as well, I'm fairly certain we're going to want to add a few to that this time around.  Keeping in mind that config won't override user config though.
[18:49] <Unit193> Eg, we may not want to remove voluemd+-sound as pa-plug wouldn't get automatically added to the panel, -application, but mate/gnome switch is fine.
[21:56] <ochosi> subh: hi, what would you like to work on?
[22:32] <bluesabre> Unit193: makes sense. We also have some migration scripts that we may need to poke to update the keyboard shortcuts and whatnot
[22:32] <ochosi> hey bluesabre 
[22:33] <Unit193> :3
[22:33] <bluesabre> hey ochosi 
[22:33] <bluesabre> hey Unit193 
[22:33] <Unit193> Hellos.
[22:33] <ochosi> bluesabre: regarding the pa-plugin, what do you wanna do regarding flocculant's suggestions for the menu?
[22:33] <bluesabre> ochosi: was planning on just trying a few different layout options and see what we like
[22:35] <bluesabre> obviously somewhat limited with using a popup menu
[22:36] <ochosi> yup
[22:36] <ochosi> i would also try not to overload it
[22:36] <bluesabre> Yup
[22:36] <ochosi> so having all of this in one row seems a little excessive:
[22:37] <ochosi> [ icon | volumescale | switch | submenu> ]
[22:37] <bluesabre> I thought I might replace the current volume indicator icons with just a generic input/output device icon on the device selection above
[22:37] <ochosi> if there is such an icon in "the icon themes" then why not
[22:38] <bluesabre> yeah
[22:38] <ochosi> it's probably not what people are used to seeing there...
[22:38] <ochosi> but it could work ok
[22:38] <bluesabre> Yeah
[22:38] <bluesabre> Current version feels unbalanced
[22:38] <bluesabre> Volume indicator on a different row from the slider also feels wrong
[22:38] <bluesabre> So thought that would be the next experiment
[22:40] <ochosi> another suggestion is to go back to a larger icon with rowspan=2
[22:41] <bluesabre> yeah
[22:41] <ochosi> also, i think with the scale next to the icon it's little superfluous to have the icon update according to the volume state (apart from muted)
[22:41] <bluesabre> yeah
[22:42] <ochosi> the scale tells you much more nicely what the actual state is
[22:42] <bluesabre> except it doesn't convey muted at all
[22:42] <bluesabre> But the switch is right next to it
[22:42] <bluesabre> So thats fine
[22:43] <bluesabre> The icon gives the clearest indication of the current state
[22:44] <bluesabre> Another option is to move the scale row to the top and have the options below (if more than 1)
[22:44] <bluesabre> The icon identifies whether it is in or out and current state
[22:44] <bluesabre> The rest is just extra
[22:45] <ochosi> the scale could convey muted, but then you would have to set it to insensitive
[22:45] <ochosi> which would be a feature loss imo
[22:45] <bluesabre> Yup
[22:45] <ochosi> because it's nice to be able to control what volume you "unmute" to
[22:45] <bluesabre> I like adjusting volume before unmuting
[22:47] <ochosi> maybe moving the output below the scale would work better
[22:47] <bluesabre> Yeah
[22:47] <ochosi> than the bold text could also be dropped
[22:47] <ochosi> because it wouldn't be a headline anymore
[22:47] <bluesabre> Sounds like an improvement
[22:47] <ochosi> would make it more readable
[22:48] <ochosi> and the volume icon would just be a boolean
[22:48] <bluesabre> Might even be necessary since I'm going to add device channels at some point
[22:48] <ochosi> i still like the idea of having the icon itself used as "mute" button, but it's not discoverable enough
[22:54] <bluesabre> It might be
[22:54] <bluesabre> More things for me to play with
[22:55] <ochosi> regarding the xubuntu cycle, do you really wanna work on pidgin?
[22:55] <bluesabre> ochosi: only if I find that the patch doesn't take days to work out
[22:55] <ochosi> just because it's on our blueprint yet again
[22:56] <ochosi> (i'd personally like it because i like the theme and it was some work too)
[22:56] <bluesabre> Yup
[22:56] <bluesabre> I'd like to have it
[22:56] <bluesabre> More things to show off
[22:56] <bluesabre> Also saw
[22:56] <bluesabre>  [xubuntu-dev] thunar: Provide more default custom actions (printing, convert to pdf): TODO
[22:56] <bluesabre> I think you added this?
[22:56] <ochosi> yeah
[22:57] <ochosi> the printing can be done for images and especially pdfs with lpr
[22:57] <ochosi> very simple one
[22:57] <ochosi> if we want libreoffice support too, it'd have to be a bash-script so we can handle both
[22:58] <ochosi> and convert to pdf would work for .docx, .ods via libreoffice too
[22:58] <ochosi> for everything else we *could* use imagemagick, but it's probably too heavy to ship on our default image just for that
[22:58] <ochosi> (at least i think we don't ship it currently)
[22:59] <ochosi> i just felt thinking about some custom actions wouldn't hurt
[22:59] <ochosi> and those two i have on every laptop of mine, so i thought i'd propose them
[23:04] <bluesabre> ochosi: sounds handy
[23:04] <bluesabre> want to submit a MP or bug report with those?
[23:05] <bluesabre> We'll need translations for those, so getting them in earlier would be better
[23:07] <ochosi> yeah, the lpr one is almost done
[23:07] <bluesabre> Unit193: want to get some fresh packaging together for  [xubuntu-dev] elementary-xfce: Split packaging for distribution improvements: TODO ? We could land it in Xubuntu first and propose it to debian
[23:08] <ochosi> still lacking the "patterns" prat
[23:09] <Unit193> bluesabre: Who'd be maintaining it in Debian?  And could try and assist.
[23:10] <bluesabre> Unit193: probably us, elementary-xfce could go into pkg-xfce
[23:13] <ochosi> iirc we discussed adding all kinds of distro logos and handling symlinking to distributor-logo via the packaging
[23:14] <ochosi> then there would be no split packaging needed
[23:14] <ochosi> or did you have anything else in mind?
[23:15] <bluesabre> basically, it's packaged now as "xubuntu-icon-theme" in Ubuntu
[23:16] <bluesabre> it could be "elementary-xfce" and "xubuntu-icon-theme" could be a branded version that just provides the alt distributor-logo to the elementary-xfce themes
[23:16] <bluesabre> or smth
[23:17] <bluesabre> Gives more flexibility to flavors and our downstreams that we don't want using our logo
[23:17] <ochosi> right, the flavors argument makes sense
[23:18] <ochosi> i think pasi already prepped everything in the icon theme
[23:18] <bluesabre> and general availability in more than *buntu means more users and maybe more contributors
[23:18] <bluesabre> He did
[23:18] <bluesabre> Just need a packaging poke
[23:18] <ochosi> so be aware of that for the next upload
[23:18] <ochosi> indeed
[23:21] <bluesabre> ochosi: I'll probably take a look at libreoffice soon and send you some missing icon notes
[23:22] <ochosi> ah right, that too
[23:22] <ochosi> the save as icon is fairly prominent...
[23:23] <bluesabre> :)
[23:27] <bluesabre> ochosi: need anything else from me?
[23:27] <Unit193> bluesabre: Oh, and general poke about all your Debian packages. :P
[23:28] <bluesabre> Unit193: indeed, need to refresh those
[23:28] <bluesabre> everything was easier when I could just svn-inject my updates
[23:28] <ochosi> bluesabre: well more patches would be nice ;)
[23:28] <Unit193> gbp is soooo much easier.
[23:29] <bluesabre> ochosi: sure thing, I'll start submitting more PRs when I can get away with symlinks or other people's work
[23:29] <bluesabre> you probably don't want my icon handiwork
[23:30] <Unit193> And you usually keep me far away from all things artwork and design too. :(
[23:31] <ochosi> symlinks should hopefully do a lot of the jobs
[23:36] <ochosi> i totally forgot how ridonculous the LO icon themes were...
[23:37] <bluesabre> :D
[23:39] <ochosi> pfff
[23:39] <ochosi> they added savemodified_extralarge.png
[23:39] <ochosi> used to be just "savemodified_large.png"
[23:40] <genii> I'm still waiting for all icons to be svg
[23:40] <bluesabre> ochosi, glad you're quick to find them though
[23:40] <ochosi> well...
[23:40] <ochosi> genii: the icons in my theme are svg
[23:40] <ochosi> they're just png-ified for LO
[23:40] <bluesabre> we should try to get these all fixed by Dec/Jan, LibreOffice 6 is due then, I believe
[23:41]  * genii pats ochosi on the back for good work
[23:41] <bluesabre> aha
[23:42] <bluesabre> Week 51 , Dec 18, 2017 - Dec 24, 2017 Libreoffice 6 UI freeze
[23:42] <bluesabre> https://wiki.documentfoundation.org/ReleasePlan/6.0
[23:43]  * bluesabre appreciates having ochosi around
[23:45] <ochosi> crap, i have no idea anymore how pull requests against LO work with their gerrit :'(
[23:45] <ochosi> anyway, time to sleep
[23:45] <ochosi> (downside of having this merged to upstream)
[23:46] <bluesabre> nighty ochosi
[23:46] <Unit193> Could be worse, could be what KDE is using. :P
[23:48] <ochosi> sucks also that Sweetshark was sacked by canonical, so no help from the desktop team anymore...