| | [ Return to Bugs & Features | Post Text | Post File | Prev | Next ]
STR #3418
| Application: | FLTK Library |
|---|
| Status: | 5 - New |
|---|
| Priority: | 1 - Request for Enhancement, e.g. asking for a feature |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | Core Library |
|---|
| Summary: | Promote current scaling factor to child processes |
|---|
| Version: | 1.4-feature |
|---|
| Created By: | chris |
|---|
| Assigned To: | Unassigned |
|---|
| Fix Version: | Unassigned |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
[ Post File ]
Trouble Report Comments:
[ Post Text ]
| |
| #1 | chris
09:49 Oct 20, 2017 |
| Seen with the demo program:
When changing the scaling factor with the shortcut keys, the spawned demo programs don't honour it, but always start with the initial scaling factor.
One idea to solve this, would be IMHO to export the current scaling factor to the FLTK_SCALING_FACTOR environment variable before.
I tried this for the demo program. But later I also thought this could be probably done in the library too, when scaling is changed.
So I add two patches: one for the demo program only, the other for the general solution.
Please take this patches only as outline, I was not entirely sure, which method(s) to use for obtaining the current scale factor in the demo program and how to best access the putenv() method present in the system driver. | |
| |
| #2 | chris
05:12 Oct 21, 2017 |
| A minor, yet important correction for the patches is neccessary:
The putenv() string must not be released, so 'static' has to be used:
static var[50]; | |
[ Return to Bugs & Features | Post Text | Post File ]
|
| |
FLTK Apps 
