Libertine Tweak Tool

TotalSonic

@doniks - the Libertine Tweak Tool arm64 beta is working well on my Volla Phone (RC channel). I like the new icon.

Best regards,
Steve Berson

doniks

thanks for the confirmation @TotalSonic

new version is now in the store. thank you very much @johndoe for making the icon!

sorry it took so long

johndoe

@doniks You're welcome and no problem

doniks

I'm happy to announce that LTT just learned how to be translated from Anne Onyme 017. Thanks a lot!

German has just been added in gitlab and French is in the works. If you feel like contributing another language (It's just a dozen strings or so, but admittedly quirky ones). Please check out the README

Pulsar33

@doniks Hello
In this topic, I raised some doubts about the usefulness of Libertine Tweak Tool regarding the Xdpi setting that allows (among other things) to increase the graphical representation of applications running in the Libertine container.

I was about to say that I was wrong when I first discovered Libertine and LTT. Indeed, I just redid some screenshots with LXTerminal and I saw that the dead zone on the right in landscape mode does NOT depend on the Xdpi setting of LTT as you can seen here :

With this application, the behavior (selection of a line of text with the mouse in this case) seems identical for an absence of Xdpi setting and for a forcing of Xdpi at 180

However, I also did some testing with Gedit (and with my CheckLog application) and I saw the following:

In fact, the dead zone is not dead, there is an offset between the mouse position and the widget grid of the application. And this depends on the Xdpi setting.

I thought the problem was limited to landscape mode but I also saw with Gedit that there are also problems in portrait mode as you can see here :

The action bar at the bottom seems to be framed on the right and in this case, we lose widgets on the left while at the top the two buttons are positioned normally, one on the left, one on the right. The left-framed menu bar loses items on the right. This happens when the Xdpi setting of 180 is the right one for other applications but not for this one.

~~Finally, I couldn't try again in windowed mode because I can't find the com.canonical.Unity8 schematics anymore (switch to OTA-22 or change on my part?)~~ Find it again. Could be able to make more tests ...

I am not saying that these errors are due to LTT but simply that LTT highlights them and in some cases the applications become unusable. I think that not all applications take into account the dpi setting (especially my CheckLog application programmed only "in pixels") and Gedit obviously has big problems on this side.

This is why I considered at the time that a single dpi setting was not the solution and that it was better to set the graphic size of each application with its own menus when possible (Font size for example).

BR
Pulsar33

doniks

ugh sounds complicated. thanks @pulsar33 for writing this up! do you see a difference in this dead zone / offset behaviour between touch and mouse? I probably need to play with this myself to understand.

doniks

@pulsar33 said in Libertine Tweak Tool:

Ok, I think I can reproduce this

It seems to me that every click or touch in the "dead zone" is interpreted as a click on that red line. So, it is always shifted.

When I adjust the dpi value so that the imaginary red line falls on highlighting selector ("Texte brut") and then I aim at "INS" the click will land on the "Texte brut"
When I open a text document full of text and start selecting text, I can move around as I want, except when I move into the "dead zone" then the selection only reaches to the red line and not further to the right.

You say you have no dead zone with 180 - can you describe how you determine that in gedit?

doniks

fwiw, it seems to me to be an issue in xmir. when I run cnee --record --mouse in lxterminal, I see that the x coordinate (third column) never goes higher than 1199 on my Nexus 7 (7 inch, 800 x 1280 pixels). thats the same in landscape, portrait, upside down portrait. also in windowed mode. then one can also nicely see that the offset is from the left of the window, not the screen.

another way to check is with xournal

Pulsar33

@doniks

@pulsar33 said in Libertine Tweak Tool:

I am not saying that these errors are due to LTT but simply that LTT highlights them and in some cases the applications become unusable

An issue exists since 3 years !
However, my understanding described above is not exactly the same as @dobey or @rodney

@pulsar33 said in Libertine Tweak Tool:

In fact, the dead zone is not dead, there is an offset between the mouse position and the widget grid of the application. And this depends on the Xdpi setting.

It seems to me that there's only a mismatch between the "display grid" and the "mouse grid"

Best regards
Pulsar33

doniks

@pulsar33 said in Libertine Tweak Tool:

An issue exists since 3 years !

Mhm, yeah, I could imagine that xmir issues are close towards the end of a long list of other priorities Thanks for sharing the link!

However, my understanding described above is not exactly the same as @dobey or @rodney

@pulsar33 said in Libertine Tweak Tool:

In fact, the dead zone is not dead, there is an offset between the mouse position and the widget grid of the application. And this depends on the Xdpi setting.

It seems to me that there's only a mismatch between the "display grid" and the "mouse grid"

strange. I think my observation matches more closely with the issue you linked

dobey

@pulsar33 said in Libertine Tweak Tool:

However, my understanding described above is not exactly the same as @dobey

I'm not sure if you're referring to the sole comment under the report about portrait width, but it was not my observation. The issue was imported from GitHub, and the comment starts off stating the GitHub username which made the comment originally.