Customer support is working?
Customer support is working?
Softmaker customer support for Linux is working? I filled twice (two and one week ago) a request for help and didn't receive any answer. Not even an automatic one.
Re: Customer support is working?
Our support team is actively available to assist you. However, we're unable to locate your support request using the email address associated with your forum account.
To help us resolve your issue promptly, please:
1. Email us directly at support@softmaker.com, or
2. Share your problem details here in this thread.
We'll be happy to assist you through either channel.
To help us resolve your issue promptly, please:
1. Email us directly at support@softmaker.com, or
2. Share your problem details here in this thread.
We'll be happy to assist you through either channel.
Re: Customer support is working?
Thanks. I will copy the email here:
**************
My laptop setup consists of two screens:
. 4K/Primary Screen, 3840x2160@150%
. Built-In/Secondary Screen, 1366x768@100%
Usually, I set the User Interface to my liking on the 4K/Primary Screen. If I move TextMaker (or PlanMaker) to the smaller screen, it scales correctly. Everything works fine. The text and user interface scale automatically to the smaller resolution.
But, if I disconnect the primary screen (e.g. taking the laptop from the docking; or, using the O.S. display configuration; rebooting or not, it doesn't matter) then:
1/ The program doesn't scale at all, keeping the 4K configuration. Which is a problem, especially on the smaller screen...
2/ When I reconnect the 4K primary screen, all dialog boxes open on the smaller Screen (not the 4K as expected) and are partially out of sight.
Usually, I have to set up the user interface before disconnecting the 4K Screen and then before connecting it back, because the problem also occurs in reverse order.
It's especially irritating on TextMaker (my main tool), but it happens with PlanMaker and Presentations.
***
Tinkering, I discovered that I can edit ~/SoftMaker/Settings/ofnconfig.ini and ~/SoftMaker/Settings/tmnxconfig.ini (or orbxconfig.ini), and adjust the LargeIcons and OnePixFontAdjust variables... But this is not an elegant solution!
***
Operating System: Fedora Linux 41; KDE Plasma Version: 6.3.3; KDE Frameworks Version: 6.12.0; Qt Version: 6.8.2; Kernel Version: 6.13.6-200.fc41.x86_64 (64-bit); Graphics Platform: Wayland; Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz; Memory: 15.4 GiB of RAM; Graphics Processor: Mesa Intel HD Graphics 520; Primary Screen: 3840x2160@150%; Secondary Screen: 1366x768@100%
**************
My laptop setup consists of two screens:
. 4K/Primary Screen, 3840x2160@150%
. Built-In/Secondary Screen, 1366x768@100%
Usually, I set the User Interface to my liking on the 4K/Primary Screen. If I move TextMaker (or PlanMaker) to the smaller screen, it scales correctly. Everything works fine. The text and user interface scale automatically to the smaller resolution.
But, if I disconnect the primary screen (e.g. taking the laptop from the docking; or, using the O.S. display configuration; rebooting or not, it doesn't matter) then:
1/ The program doesn't scale at all, keeping the 4K configuration. Which is a problem, especially on the smaller screen...
2/ When I reconnect the 4K primary screen, all dialog boxes open on the smaller Screen (not the 4K as expected) and are partially out of sight.
Usually, I have to set up the user interface before disconnecting the 4K Screen and then before connecting it back, because the problem also occurs in reverse order.
It's especially irritating on TextMaker (my main tool), but it happens with PlanMaker and Presentations.
***
Tinkering, I discovered that I can edit ~/SoftMaker/Settings/ofnconfig.ini and ~/SoftMaker/Settings/tmnxconfig.ini (or orbxconfig.ini), and adjust the LargeIcons and OnePixFontAdjust variables... But this is not an elegant solution!
***
Operating System: Fedora Linux 41; KDE Plasma Version: 6.3.3; KDE Frameworks Version: 6.12.0; Qt Version: 6.8.2; Kernel Version: 6.13.6-200.fc41.x86_64 (64-bit); Graphics Platform: Wayland; Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz; Memory: 15.4 GiB of RAM; Graphics Processor: Mesa Intel HD Graphics 520; Primary Screen: 3840x2160@150%; Secondary Screen: 1366x768@100%
Re: Customer support is working?
About #1: There isn't any linux applications that scale as you want them too. No application is truly 4k aware. You may ask yourself: Why does KDE Apps remember if they are 4k or not? Because KDE saves a file that says foy screen X, morel Y do Z. If you here to connect a different screen that is not X but Z it would just go back to the default. Same goes for Gnome and any other desktop. Also keep in mind that scaling under wayland can be unreliable.
About 2: This is due of how kwin works. Kwin always "remembers" where the window was last time (screen, position, size...). It does not care what screen is set as "main".
About 2: This is due of how kwin works. Kwin always "remembers" where the window was last time (screen, position, size...). It does not care what screen is set as "main".
Re: Customer support is working?
All Linux applications I use scale correctly. Only Texmaker and Planmaker have that issue.
You can check KDE Kate, Telegram Desktop, Firefox, Darktable or Joplin.
It's the same about the window position. For a program opened in screen 'x', all dialogs are expected on screen 'x', not between screens. The same if you move the program from one screen to the other.
You can check KDE Kate, Telegram Desktop, Firefox, Darktable or Joplin.
It's the same about the window position. For a program opened in screen 'x', all dialogs are expected on screen 'x', not between screens. The same if you move the program from one screen to the other.
Re: Customer support is working?
Because all the applications do you mention use Qt (Kate, Telegram) or GTK (Firefox, darktable). Softmaker Office do not use one of those toolkits, and even so, GTK is famous for being awful at stalling. Only recently they addressed some of the shortcomings of their scaling method.
For the window position issue, have a chat with the folks of KDE. The yare the ones who came with the brilliant idea of: Let's start the application, and all related windows, at the last screen it was positioned. You could make a rule so kwin places SMO where you want.
For the window position issue, have a chat with the folks of KDE. The yare the ones who came with the brilliant idea of: Let's start the application, and all related windows, at the last screen it was positioned. You could make a rule so kwin places SMO where you want.
Re: Customer support is working?
Window position issue: it doesn't work if you close and reopen the application in the original screen, anyway dialogs will open in the middle of both screens. You must reboot.
Regarding the scaling issue: I wrote a bash script that get the number of active screens and modify ofnconfig.ini and tmnxconfig.ini accordingly before opening TextMaker. It works for my specific setting. Surely it will be easy for SoftMaker programmers to do something in the next release.
Regarding the scaling issue: I wrote a bash script that get the number of active screens and modify ofnconfig.ini and tmnxconfig.ini accordingly before opening TextMaker. It works for my specific setting. Surely it will be easy for SoftMaker programmers to do something in the next release.
Re: Customer support is working?
Traditionally this is how it works: You set scaling in KDE. KDE, itself, does not do scaling, what it does is it goes and set the scaling for QT and GTK apps. And then consider each toolkit has its way of doing scaling. GTK, for instance, until very recently, was unable to do fractional scaling. QT only works with fractional scaling. EFL can do fractional and DPI scaling. Now... consider for a minute that SMO had to go and check for each desktop and window manager how scaling was performed, and what that value is it so it could set it to whatever it is?
I understand Fedora only ships KDE with wayland. I do not care what KDE developers say about wayland being ready. It isn't and their implementation shows. If you go and check their changelogs you realize since they default KDE to wayland all they have done is fix bugs and re-implement features that were present on x11. What you are experiencing could be, easily, one of those "papercuts" of the kwin_wayland. I think is just a placement issue of kwin_wayland. You could see if you can reproduce this on kwin_x11 or any other window manager/desktop
I understand Fedora only ships KDE with wayland. I do not care what KDE developers say about wayland being ready. It isn't and their implementation shows. If you go and check their changelogs you realize since they default KDE to wayland all they have done is fix bugs and re-implement features that were present on x11. What you are experiencing could be, easily, one of those "papercuts" of the kwin_wayland. I think is just a placement issue of kwin_wayland. You could see if you can reproduce this on kwin_x11 or any other window manager/desktop