Too bright pulley menu lines in 3.2.0 Torronsuo

Question

18

Too bright pulley menu lines in 3.2.0 Torronsuo

asked 2019-11-01 08:53:56 +0200

Yenya
922 ●20 ●28 ●33

updated 2019-11-05 05:05:55 +0200

Tanghus
10524 ●85 ●118 ●125

https://github.com/tanghu...

Hello,

is it possible to lower the brightness of the pulley menu lines at the screen edges to the levels they were before 3.2.0? It gets pretty annoying especially at night while using an application which has been carefully tuned to the night mode (e.g. FBreader). The bright blue line at the top of the screen hurts my eyes :-). I think the original version was better - it was still visible, but not so much to hinder the overall usability. Thanks!

(That said, I highly appreciate receiving OS updates even for such an old device like Jolla 1)

-Yenya

edit retag flag offensive close delete

Comments

1

Agreed, it's too bright.

Perhaps to leave it as it was before 3.2 update but allow it to blink 2 or 3 times for the first 3 times the app is used, making the 'newer' user aware of its availability, as is the given idea/explanation per the release notes.

Spam Hunter ( 2019-11-01 19:28:47 +0200 )edit

I can hardly see any difference. (I changed the tags from bug to feature-request and pulley-menu.)

Tanghus ( 2019-11-05 05:03:23 +0200 )edit

Quite right@Tanghus, I didn't notice the 'bug' tag. But the pulley menu tab is most certainly brighter than it was before SFOS 3.2.

I've made a universal remote control for my Jolla1 to control RF lamps and IR mechanisms (hifi, etc), for which i created a 'dimming' mode which works nicely, except now though, I have these horrible laser like lines at the top and bottom of my first page.

I've been hunting to try and find the offending code/files that were changed, no luck yet.

Spam Hunter ( 2019-11-05 11:57:54 +0200 )edit

As for the "bug" tag: I consider the new behaviour being a usability/UX bug (and also a regression, because it was OK in previous versions).

Yenya ( 2019-11-05 12:25:31 +0200 )edit

3

The effect is intentional, so in my opinion, it is not a bug but could certainly be labelled 'regression'.

Spam Hunter ( 2019-11-05 12:45:04 +0200 )edit

Agreed, it's too bright.
Perhaps to leave it as it was before 3.2 update but allow it to blink 2 or 3 times for the first 3 times the app is used, making the 'newer' user aware of its availability, as is the given idea/explanation per the release notes.
Spam Hunter ( 2019-11-01 19:28:47 +0200 )edit
I can hardly see any difference. (I changed the tags from bug to feature-request and pulley-menu.)
Tanghus ( 2019-11-05 05:03:23 +0200 )edit
Quite right@Tanghus, I didn't notice the 'bug' tag. But the pulley menu tab is most certainly brighter than it was before SFOS 3.2.
I've made a universal remote control for my Jolla1 to control RF lamps and IR mechanisms (hifi, etc), for which i created a 'dimming' mode which works nicely, except now though, I have these horrible laser like lines at the top and bottom of my first page.
I've been hunting to try and find the offending code/files that were changed, no luck yet.
Spam Hunter ( 2019-11-05 11:57:54 +0200 )edit
As for the "bug" tag: I consider the new behaviour being a usability/UX bug (and also a regression, because it was OK in previous versions).
Yenya ( 2019-11-05 12:25:31 +0200 )edit
The effect is intentional, so in my opinion, it is not a bug but could certainly be labelled 'regression'.
Spam Hunter ( 2019-11-05 12:45:04 +0200 )edit

Answer 1

3

answered 2020-01-05 00:24:21 +0200

kuba77

478 ●10 ●18 ●20

I made a patch which bring back brightness from 3.1 https://coderus.openrepos.net/pm2/project/pulley-menu-lines-brightness

edit flag offensive delete publish link

Comments

I made this too yesterday night. As it was just too easy to patch (thanks @edz). But I did not get the confirmation e-mail from sign up process yet ... and I see yours is much more sophisticated :)

peterleinchen ( 2020-01-05 00:44:51 +0200 )edit

and here's a great example of why i don;t bother to upload any more, when people just take work/ideas from others and don't even care to mention the original source in the description, Rude, plain rude.

Spam Hunter ( 2020-01-05 01:56:42 +0200 )edit

1

@peterleinchen I took that file from 3.1.0.12 (I must find and download ROM with this version SFOS and extract the file), used diff with 3.2.1.20 and did make little edits.

@Edz I'm sorry if you feel that I should mention you :-( I usually do it but my patch don't change/delete the line you suggest. Same qml file is modified by Ancelad's patches which brings old Pulley menu style from SailfishOS 1.1. So maybe I (we) should mention him too?

kuba77 ( 2020-01-05 03:08:33 +0200 )edit

1

Fair play, seems I misunderstood your intentions @kuba77, please ignore me, I'm just being a grouchy old man for five minutes!, I should have checked out your patch before opening my gob...er, typing,...you get the idea.

Spam Hunter ( 2020-01-05 11:01:31 +0200 )edit

Answer 2

2

answered 2019-11-07 15:55:36 +0200

DrYak

9624 ●93 ●134 ●128

http://www.sympato.ch/

Not a solution but a workaround

The old pulley style (my favourite) happens to be not so bright as the post-3.2 pulleys.

So if you install the return old pulley menu patch in patch manager, you happen to get a not too bright pulley menu.

edit flag offensive delete publish link

Comments

Now somebody could write a patch that bring configurable brightness in new pulley menus.

i.e.: leave the default ultra-bright to help newbie users
let users make it dimmer if they want

DrYak ( 2019-11-07 15:56:47 +0200 )edit

A good workaround... but still relying on a community patch (and the activity of its developer). I use it from the beginning but it was unavailable few months ago...

A must have for me, with "Topmenu control" and "Launcher combined" (but sadly not maintained since SFOS 3.0).

PhixGre ( 2019-11-07 18:35:30 +0200 )edit

Accepted Answer

2

answered 2020-01-02 19:45:16 +0200

Spam Hunter

11677 ●187 ●289 ●324

updated 2020-01-05 01:46:22 +0200

Here is one solution, as I do not see Jolla removing this.

Navigate to /usr/lib/qt5/qml/Sailfish/Silica/private/PulleyMenuBase.qml to line 446

Find the line which reads: color: pulleyBase.highlightColor and comment out the line so it looks like this;

    // color: pulleyBase.highlightColor

Restart lipstick to make the changes stick and enjoy the original muted look of the pulley menu bar.

For those who don't see much difference, I think my favourite dark theme shows this nicely. The blue part is to allow the white bar to be seen when viewed against a white background, like here on TJC;

image description

edit flag offensive delete publish link

Comments

@Edz

You gave me a short heart attack last night :D.
But I guess my own fault as I stepped one or two times in this already.

and hash out the line

Never ever hash (#) lines in qml! It will break everything. Use C/C++ comments.

Here it was really everything. After lipstick restart nothing came up again. No menu, no application, nothing . Even top menu was broken. But at least I could shut down and let it rest and charging ( even no led charging light ) to the morning and corrected via recovery shell :D

peterleinchen ( 2020-01-05 00:50:33 +0200 )edit

1

Oops!, poor choice of words, I didn't consider the difference between ''hash' and 'comment out' at the time of writing, my apologies for the hassle caused.

I always edit via SSH (USB cable) so no matter what happens (mistakes) I can always access the file and repair it.

Original answer updated to reflect your comments @peterleinchen

Spam Hunter ( 2020-01-05 01:42:21 +0200 )edit

No need to apologize. I should have known myself editing a QML especially as this has happened before to me! (always/mainly do it directly on the phone)

I was upstairs in the bedroom and too sleepy/lazy ...

peterleinchen ( 2020-01-05 10:07:29 +0200 )edit

Too bright pulley menu lines in 3.2.0 Torronsuo

Comments

3 Answers

Comments

Not a solution but a workaround

Comments

Comments

Question tools

Stats

Related questions

Too bright pulley menu lines in 3.2.0 Torronsuo

Comments

3 Answers

Comments

Not a solution but a workaround

Comments

Comments

Question tools

Public thread

Stats

Related questions