[00:19] <ubptgbot> xRed8beardx was added by: xRed8beardx
[04:03] <ubptgbot> LowestDp was added by: LowestDp
[06:24] <ubptgbot> <YougoChats> mv or rn the entire .gimp folder and start gimp vanilla. unless you have tons of customisations that take forever to reconstruct of course
[06:27] <ubptgbot> <YougoChats> at least you may fetch a clean `sessionrc` and compare the lines
[06:27] <ubptgbot> <YougoChats> [Edit] 'mv' the entire .gimp folder and start gimp vanilla. unless you have tons of customisations that take forever to reconstruct of course
[06:28] <ubptgbot> <YougoChats> [Edit] `mv` the entire .gimp folder and start gimp vanilla. unless you have tons of customisations that take forever to reconstruct of course
[06:43] <ubptgbot> <Aury88> @malditobastardo [I don't know. Using gimp was before a PIA and now its difficult to open the tool …], I wonder if libhandy would be able to improve a situation like that🤔
[10:32] <ubptgbot> <Fuseteam> Under wayland, perhaps
[11:02] <ubptgbot> <malditobastardo> That's the hope
[11:22] <ubptgbot> <dohbee> gimp 2.8 is gtk+ 2.0, so no
[11:23] <ubptgbot> <dohbee> it would require X still
[15:02] <ubptgbot> <Fuseteam> Oops
[15:42] <flaburgan> dohbee gimp will reach gtk 3 soon
[15:42] <flaburgan> most of it is already ported
[16:13] <ubptgbot> <dohbee> @flaburgan [dohbee gimp will reach gtk 3 soon], not in the xenial repo though
[16:14] <flaburgan> hm
[16:14] <flaburgan> that's probably true
[16:16] <ubptgbot> LEOLEOSP was added by: LEOLEOSP
[16:17] <ubptgbot> <LEOLEOSP> Hey guys, … I would like to take a closer look at how touch events are handled, e.g. scrolling with my fingers and so on. … Can someone point me to the code (or the project) where this is handled?
[16:20] <ubptgbot> <dohbee> what do you mean by "handled" exactly?
[16:27] <ubptgbot> <Fuseteam> Read as input?
[16:27] <ubptgbot> <dohbee> the kernel gives input events. toolkits and applications react to those as they see fit
[16:29] <ubptgbot> <Fuseteam> So that moves to the place where the reaction is coded xD
[16:29] <ubptgbot> <Fuseteam> [Edit] So that moves the question to "where the reaction is coded?" xD
[16:30] <ubptgbot> <Fuseteam> [Edit] So that moves the question to "where tis he reaction coded?" xD
[16:30] <ubptgbot> <Fuseteam> [Edit] So that moves the question to "where is he reaction coded?" xD
[16:30] <ubptgbot> <Fuseteam> [Edit] So that moves the question to "where is the reaction coded?" xD
[16:33] <ubptgbot> <Fuseteam> I think in the terminal app at least part of it is code in Terminal.qml
[16:55] <ubptgbot> <dohbee> well, terminal app is simply getting the events and choosing to do something with them in the UI
[16:56] <ubptgbot> <dohbee> a different app may choose to do something differently
[16:56] <ubptgbot> <Fuseteam> True :3
[17:23] <ubptgbot> <LEOLEOSP> So my general goal would be to "adjust" some parameters (I know it will be harder than that) such that scrolling doesn't feel so... sloppy? Bad? I don't know how else to describe it.
[17:24] <ubptgbot> <LEOLEOSP> I guess QT "handles" scrolling and stuff? The kernel just gives the information "touch event at x,y", etc.?
[17:26] <ubptgbot> <dohbee> @LEOLEOSP [So my general goal would be to "adjust" some parameters (I know it will be harde …], the fix for that is likely not related to the touch handling code
[17:27] <ubptgbot> <dohbee> most performance issues are likely either in the apps themselves or in ubuntu-ui-toolkit (or in qt itself perhaps)
[17:28] <ubptgbot> <dohbee> it also feels differently across different devices currently because of this
[17:29] <ubptgbot> <LEOLEOSP> No I don't mean the performance issues, as a concrete example I mean the deceleration when you scroll and let go of the screen feels really wrong. You can't read the text, but the animation is continuing smoothly, do you know what I mean? … I am using a Nexus 5 btw.
[17:30] <ubptgbot> <LEOLEOSP> It just doesn't feel natural, it scrolls way too long after you let go, in my opinion.
[17:30] <ubptgbot> <dohbee> seems ok here on my nexus 5, in at least the ubports app (but it's not too far to scroll)
[17:30] <ubptgbot> <dohbee> but the answer i guess is "it depends"
[17:31] <ubptgbot> <Fuseteam> @LEOLEOSP [It just doesn't feel natural, it scrolls way too long after you let go, in my op …], In which app?
[17:32] <ubptgbot> <dohbee> hmm, the "software licenses" list in system-settings feels fine here
[17:32] <ubptgbot> <Fuseteam> Teleports and dash feel fine here
[17:35] <ubptgbot> <LEOLEOSP> Guess it's because I am used to Android, then... … Anyhow, so you think this deceleration is handled in ubuntu-ui-toolkit?
[17:40] <ubptgbot> <Javacookies> maybe something related to the previous bug of hovering which was worked around without a proper fix
[17:41] <ubptgbot> <Fuseteam> @LEOLEOSP [Guess it's because I am used to Android, then... … Anyhow, so you think this decel …], You didn't answer my question :p
[17:43] <ubptgbot> <LEOLEOSP> @Fuseteam [You didn't answer my question :p], I guess in every app, since it's all handled the same? … Try the settings app, and scroll very softly and release your finger. It scrolls on for like a second before it stops. I think this feels unnatural
[17:45] <ubptgbot> <Fuseteam> You experience this in every app?
[17:46] <ubptgbot> <Fuseteam> I cannot confirm this behavior
[17:47] <ubptgbot> <Fuseteam> Have you tried rebooting?
[17:47] <ubptgbot> <dohbee> @LEOLEOSP [I guess in every app, since it's all handled the same? … Try the settings app, and …], eh?
[17:48] <ubptgbot> <dohbee> it feels basically the same as my pixel with android feels
[17:52] <ubptgbot> <LEOLEOSP> Mhh okay I just did some further testing, the settings app seems definitely to be the worst offender? Why does it feel so different scrolling there compared to the other apps?
[17:52] <ubptgbot> <dohbee> i don't know. it's hard to know what you mean, since it feels fine here
[17:53] <ubptgbot> <Fuseteam> @LEOLEOSP [Mhh okay I just did some further testing, the settings app seems definitely to b …], Which part?
[17:53] <ubptgbot> <dohbee> mmm, the main page does feel off, but not sure why
[17:53] <ubptgbot> <Javacookies> that's an adjustable property wth flickables right?
[17:54] <ubptgbot> <Fuseteam> It does?
[17:54] <ubptgbot> <Javacookies> inertia or momentum or something
[17:54] <ubptgbot> <Javacookies> LOl
[17:54] <ubptgbot> <Javacookies> I'm bad at physics
[17:54] <ubptgbot> <Fuseteam> Probably momentum
[17:55] <ubptgbot> <dohbee> inertia
[17:55] <ubptgbot> <Fuseteam> Inertia is a type of mass......wait what?👀
[17:56] <ubptgbot> <TotalSonic> With the recent changes in RC channel for Libertine apps to "flatten all windows" - I've found some apps now work better and some apps work worse.  Since one of the capabilities I still find lacking in UT native apps is for a full featured text editor (even though I think tedit, uWriter and uEdit are great to have) - I've found my old
[17:56] <ubptgbot> Libertine option is no longer working as well - but luckily `gedit` is now working a lot better.
[17:56] <ubptgbot> <TotalSonic> [Edit] With the recent changes in RC channel for Libertine apps to "flatten all windows" - I've found some apps now work better and some apps work worse.  Since one of the capabilities I still find lacking in UT native apps is for a full featured text editor (even though I think tedit, uWriter and uEdit are great to have) - I've found
[17:56] <ubptgbot> my old Libertine option of `medit` is no longer working as well - but luckily `gedit` is now working a lot better.
[17:57] <ubptgbot> <Fuseteam> Hmmm
[17:57] <ubptgbot> <dohbee> @Fuseteam [Inertia is a type of mass......wait what?👀], inertia is not a type of mass. it's a property based on mass and other things. but anyway
[17:58] <ubptgbot> <TotalSonic> In response to my own post above:  With UT I've found the best attitude to have if one wishes to use it as a daily driver is not to get attached to specific apps - but rather adapt to what is avaiable that provides the functions that are desired.
[17:59] <ubptgbot> <LEOLEOSP> @Javacookies [that's an adjustable property wth flickables right?], What are flickables?
[17:59] <ubptgbot> <dohbee> @LEOLEOSP [What are flickables?], UI components provided by Qt in QML
[18:08] <ubptgbot> <dohbee> @Javacookies [inertia or momentum or something], some velocity and overshoot properties it looks like, but have to change code it seems
[18:10] <ubptgbot> <Javacookies> yes, and as I mentioned, we also had an issue with hover which I believe wasn't fixed properly and that might be affecting the scrolling
[18:14] <ubptgbot> <dohbee> i think there is maybe an issue in system-settings main page itself; because the "software licenses" list for example feels just fine
[18:14] <ubptgbot> <dohbee> but main settings list feels "sticky"
[18:18] <ubptgbot> <dohbee> meh, and it's compiled into the binary as a resource
[18:58] <ubptgbot> <malditobastardo> @TotalSonic [In response to my own post above:  With UT I've found the best attitude to have …], Totally agree
[19:06] <ubptgbot> <LEOLEOSP> I see, thanks for your help 👍
[19:44] <ubptgbot> Root@Localhost Oliveira🏁😎 was added by: Root@Localhost Oliveira🏁😎
[19:44] <ubptgbot> <Root@Localhost Oliveira🏁😎> ❗️Get Your Earn 9.99% Interest Ethereum Per Day - 100% Asset-Backed Guarantee … ❗️Join and get your guaranteed 9.99% interest per day! … ✅More info is here👉  https://ethereum-funds.com
[19:46] <ubptgbot> <TotalSonic> @Root@Localhost Oliveira🏁😎 [❗️Get Your Earn 9.99% Interest Ethereum Per Day - 100% Asset-Backed Guarantee … ❗ …], spam
[19:47] <ubptgbot> <TotalSonic> spam above
[19:47] <ubptgbot> <Fuseteam> Bleh
[19:47] <ubptgbot> <Fuseteam> @dohbee
[19:51] <ubptgbot> <Fuseteam> Dang that's thorough
[20:11] <ubptgbot> PitfallYKMR was added by: PitfallYKMR