Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Adding more Qt env vars? #503

Open
stefonarch opened this issue Feb 25, 2024 · 4 comments · May be fixed by #504
Open

Adding more Qt env vars? #503

stefonarch opened this issue Feb 25, 2024 · 4 comments · May be fixed by #504

Comments

@stefonarch
Copy link
Member

Looking at plasma 6 I found those, added explanations I found. Maybe some of them could or should be added in startlxqt. The last one could be interesting for mobile maybe.

QT_ACCESSIBILITY=1

The QT_ACCESSIBILITY environment variable, when set to 1, enables accessibility features in Qt-based applications. These features are designed to improve usability for individuals with disabilities by providing support for assistive technologies such as screen readers and magnifiers.

QT_EXCLUDE_GENERIC_BEARER=1

The QT_EXCLUDE_GENERIC_BEARER environment variable, when set to 1, excludes the generic network bearer plugin in Qt applications. This plugin is responsible for managing network connections in a platform-independent manner. By excluding it, Qt applications may rely solely on platform-specific network plugins, potentially optimizing performance or compatibility in certain environments.

QT_AUTO_SCREEN_SCALE_FACTOR=0

The QT_AUTO_SCREEN_SCALE_FACTOR environment variable, when set to 0, disables automatic scaling of the user interface based on the screen's pixel density or resolution in Qt applications. This means that the application won't automatically adjust its interface elements to match the screen's characteristics, allowing developers more control over how the UI is displayed on different screens.
@tsujan
Copy link
Member

tsujan commented Feb 25, 2024

I don't know about the other EVs, but a nonzero value for QT_AUTO_SCREEN_SCALE_FACTOR can cause a hassle. I agree with adding all of them.

@tsujan
Copy link
Member

tsujan commented Feb 25, 2024

I didn't find QT_AUTO_SCREEN_SCALE_FACTOR for Qt6: https://doc.qt.io/qt-6/highdpi.html#environment-variable-reference

@stefonarch, do you have Qt6 links for the other two?

@stefonarch
Copy link
Member Author

stefonarch commented Feb 26, 2024 •
edited
Loading

Looks like bearer is removed?
https://forum.qt.io/topic/122926/qt-5-to-6-and-bearer-management
https://doc.qt.io/qt-6/network-changes-qt6.html#bearer-management-is-removed

Looks like QT_AUTO_SCREEN_SCALE_FACTOR is qt5 only too:
https://doc.qt.io/qt-5/highdpi.html

I saw this in qt6: QT_USE_PHYSICAL_DPI=1

But as there will be qt5 apps adding them with comments?

@tsujan
Copy link
Member

tsujan commented Feb 26, 2024

Then I guess there remains nothing to do.

With LXQt 2.0, Qt5 apps will be supported well as long as the user installs or doesn't remove the latest Qt5-based lxqt-qtplugin, libqtxdg and libfm-qt. That was the plan we agreed on from the start, without supporting Qt5 in new codes themselves.

@stefonarch stefonarch linked a pull request Feb 26, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update env vars stefonarch/lxqt-session
2 participants
@tsujan @stefonarch