Hi,
I recently upgraded to Beta 10 and now my stuff seems to be not DPI aware anymore. Is it possibly broken?
DPI awareness broken?
DPI awareness broken?
Last edited by jacdelad on Tue Jun 21, 2022 1:06 pm, edited 1 time in total.
PureBasic 6.04/XProfan X4a/Embarcadero RAD Studio 11/Perl 5.2/Python 3.10
Windows 11/Ryzen 5800X/32GB RAM/Radeon 7770 OC/3TB SSD/11TB HDD
Synology DS1821+/36GB RAM/130TB
Synology DS920+/20GB RAM/54TB
Synology DS916+ii/8GB RAM/12TB
Windows 11/Ryzen 5800X/32GB RAM/Radeon 7770 OC/3TB SSD/11TB HDD
Synology DS1821+/36GB RAM/130TB
Synology DS920+/20GB RAM/54TB
Synology DS916+ii/8GB RAM/12TB
Re: DPI arlwareness broken?
Hello jacdelad,
your question should have more effect on the bug section, hoping it is not a big problem. The dpi awareness gives headaches sometimes...
your question should have more effect on the bug section, hoping it is not a big problem. The dpi awareness gives headaches sometimes...
Re: DPI arlwareness broken?
Hi Olli,
I am not sure if it's a bug. I just realized, that my Ribbon Module is not rendered correctly anymore, no matter if I turn dpi awareness on or off (it had to be turned on before).
I am not sure if it's a bug. I just realized, that my Ribbon Module is not rendered correctly anymore, no matter if I turn dpi awareness on or off (it had to be turned on before).
PureBasic 6.04/XProfan X4a/Embarcadero RAD Studio 11/Perl 5.2/Python 3.10
Windows 11/Ryzen 5800X/32GB RAM/Radeon 7770 OC/3TB SSD/11TB HDD
Synology DS1821+/36GB RAM/130TB
Synology DS920+/20GB RAM/54TB
Synology DS916+ii/8GB RAM/12TB
Windows 11/Ryzen 5800X/32GB RAM/Radeon 7770 OC/3TB SSD/11TB HDD
Synology DS1821+/36GB RAM/130TB
Synology DS920+/20GB RAM/54TB
Synology DS916+ii/8GB RAM/12TB
Re: DPI awareness broken?
I have poor control of the DPI awareness. I understand how it works, but I waste time adapting it. There is also this difference in treatment between a new source file and a saved file: it changes, the result is not always fixed, and there is no control variable to ensure support or not...
Re: DPI awareness broken?
I confirm. I have two source files in front of me. They are exactly the same. The 1st has undergone an activation of the DPI option, then a deactivation of this DPI option, while the other has not undergone a change of DPI option: the result is different.
Problem #1 : DPI is a 3-characters keyword, what it is forbidden in the search option of the forum.
Problem #2: Is the problem on the IDE ? Or on the compiler ?
Problem #3: Is the problem on Windows management (no link with pureBasic), or on pureBasic ?Same IDE meta datas in the file, but full different result. Absolutely without logic rule...
It is even incredible : active each DPI option for each source = same result. Then switch off each DPI option for each source = different result.
2 same little programs exactly...
https://m.youtube.com/watch?v=NaT5z0-tBsg
Demo PB 5.73 LTS x64
No I cannot... I try a third...
1) IDE [New]...
2) I copy from the "right" source, and paste it to the new one...
3) Run = wrong !
I try a fourth...
Run = wrong
I switch on DPI on the third...
Synthesis of the 4 sources...
dpiAware.pb [no DPI] =OK
toDel.pb [no DPI] =WRONG
{new} [DPI] =OK
{new} [no DPI] =WRONG
truth table...
0 = 1
0 = 0
1 = 1
0 = 0
I give up...
Problem #1 : DPI is a 3-characters keyword, what it is forbidden in the search option of the forum.
Problem #2: Is the problem on the IDE ? Or on the compiler ?
Problem #3: Is the problem on Windows management (no link with pureBasic), or on pureBasic ?
Code: Select all
;1/4 of the desktop sized borderless window
ExamineDesktops()
w = DesktopUnscaledX(DesktopWidth(0) / 2)
h = DesktopUnscaledY(DesktopHeight(0) / 2)
OpenWindow(0, 0, 0, w, h, "", #PB_Window_Borderless)
Repeat
Until WaitWindowEvent() = #PB_Event_LeftClick
It is even incredible : active each DPI option for each source = same result. Then switch off each DPI option for each source = different result.
2 same little programs exactly...
https://m.youtube.com/watch?v=NaT5z0-tBsg
Demo PB 5.73 LTS x64
No I cannot... I try a third...
1) IDE [New]...
2) I copy from the "right" source, and paste it to the new one...
3) Run = wrong !
I try a fourth...
Run = wrong
I switch on DPI on the third...
Synthesis of the 4 sources...
dpiAware.pb [no DPI] =OK
toDel.pb [no DPI] =WRONG
{new} [DPI] =OK
{new} [no DPI] =WRONG
truth table...
0 = 1
0 = 0
1 = 1
0 = 0
I give up...