Problem with scale ...
 
Notifications
Clear all

Problem with scale and layout set to 150%

11 Posts
3 Users
0 Reactions
440 Views
(@tof0006)
Active Member Registered
Joined: 4 months ago
Posts: 3
Topic starter  

Hi

First of all, thanks Glenn for your work on this very useful tool. I love it.
I haven't found a similar topic, but I maybe haven't looked for the right tags.
I'm having a display problem with the url text when the scale is set to 150%.
I'm using v3.13.1.
I've just seen that there's a 3.13.2 version. I'm gonna try but I'm posting in case there's a solution.
Here's my full desktopinfo.ini file:

COMMENT=color:%white%,style:w,font-size:100%,text:INFORMATIONS SYSTEME
#DATETIME=interval:10,display:%9 %10
COLOR=%White%
COMMENT=color:%White%
HOST
BOOTTIME
USER
REGISTRY=tree:0,text:Système,key:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProductName
NETWORKINTERFACES=interval:30,operstatus:1,iftype:6 71,row-text:%2,display:%8
LOGICALDRIVES=interval:5,diskio:0,font-size:100%,chart:bar max:100 series1:7 threshold:75,alarms:(%11 ge 10000000 0000f0)(%13 ge 10000000 0000f0)(%7 ge 90 0070f0),row-text:Drive %1: (%2)| %3,display:%6[1.0B]B / %5[1.0B]B
COMMENT=color:%White%
COMMENT=color:%white%,style:w,font-size:100%,text:POUR JOINDRE LE SERVICE INFORMATIQUE
COMMENT=color:%White%
CONTROL=type:1,color:%white%,text:Email,display:servicedesk@xxxx.xx,uri:mailto:servicedesk@xxxx.xx
TEXT=text:Téléphone,display:+33 (0)x xx xx xx xx
CONTROL=type:1,color:%white%,text:Suivi des tickets JIRA,display:cliquez ici,uri: removed link
COMMENT=color:%White%
CONTROL=type:1,color:%white%,text:Doc. Outils 365,display:cliquez ici,uri: removed link

The result is attached in the topic.
Is there a solution to this or not yet?

Thanks for your help

This topic was modified 4 months ago by Tof0006

   
Quote
Topic Tags
(@rtruss)
Trusted Member Registered
Joined: 4 years ago
Posts: 74
 

OH yeah, scale, that can be VERY picky!  Due to all the different vendors and models we use it took a loooong time to build a config that would cover the 80/20 or 90/10 ratios.  Check the manual for the BEGIN-ONLOAD/END-ONLOAD info.  Below is what I ended up doing to cover the bases.  Hope it helps.

 

[items]
#NAV=global:-1,font-face:wingdings,caption-prev:ç,caption-home:ÿ,caption-next:è,font-size:14
NAV=global:-1,font-face:webdings,caption-prev:3,caption-home:=,caption-next:4,font-size:14
BEGIN-ONLOAD
    MONITOR=set:Hres=%4
    MONITOR=set:Vres=%5
    MONITOR=set:PriMon=%6
    MONITOR=set:DPI=%7
     
    # Settings for 150% DPI
    IF=value1:%DPI%,comp:eq,value2:144,eval:8
    width=440
    font-size=12
    SET=key:ControlFontSize,value:80%
    SET=key:HNLeft,value:150
    SET=key:ToolsLeft,value:10
    SET=key:Tools2Left,value:218
    SET=key:ToolsWidth,value:200
    SET=key:BRNWidth,value:226

    # Settings for 125% DPI
    IF=value1:%DPI%,comp:eq,value2:120,eval:8
    width=480
    font-size=14
    SET=key:ControlFontSize,value:60%
    SET=key:HNLeft,value:160
    SET=key:ToolsLeft,value:20
    SET=key:Tools2Left,value:240
    SET=key:ToolsWidth,value:200
    SET=key:BRNWidth,value:226

    # Settings for 100% DPI
    IF=value1:%DPI%,comp:eq,value2:96,eval:8
    width=350
    font-size=10
    SET=key:ControlFontSize,value:100%
    SET=key:HNLeft,value:125
    SET=key:ToolsLeft,value:12
    SET=key:Tools2Left,value:180
    SET=key:ToolsWidth,value:140
    SET=key:BRNWidth,value:150

    # Settings for 2560 hres and 100% DPI
    #IF=value1:%DPI%,comp:eq,value2:96,eval:7 (if using place right beforefont-size setting)
    IF=value1:%Hres%,comp:eq,value2:2560,eval:8
    WIDTH=380    
    font-size=11
    SET=key:ControlFontSize,value:90%
    SET=key:HNLeft,value:140
    SET=key:ToolsLeft,value:20
    SET=key:Tools2Left,value:180
    SET=key:ToolsWidth,value:140
    SET=key:BRNWidth,value:140  

    # Settings for 2880 hres and 200% DPI
    IF=value1:%Hres%,comp:eq,value2:2880
    WIDTH=700
    IF=value1:%DPI%,comp:eq,value2:192,eval:7
    font-size=20
    SET=key:ControlFontSize,value:60%
    SET=key:HNLeft,value:210
    SET=key:ToolsLeft,value:20
    SET=key:Tools2Left,value:320
    SET=key:ToolsWidth,value:260
    SET=key:BRNWidth,value:280

    # Settings for 3000 hres and 200% DPI
    IF=value1:%Hres%,comp:eq,value2:3000
    WIDTH=750
    IF=value1:%DPI%,comp:eq,value2:192,eval:7
    font-size=20
    SET=key:ControlFontSize,value:55%
    SET=key:HNLeft,value:270
    SET=key:ToolsLeft,value:20
    SET=key:Tools2Left,value:320
    SET=key:ToolsWidth,value:280
    SET=key:BRNWidth,value:280

    # Settings for 3840 hres and 200% DPI
    IF=value1:%Hres%,comp:eq,value2:3840
    WIDTH=750
    IF=value1:%DPI%,comp:eq,value2:192,eval:7
    font-size=20
    SET=key:ControlFontSize,value:55%
    SET=key:HNLeft,value:270
    SET=key:ToolsLeft,value:20
    SET=key:Tools2Left,value:320
    SET=key:ToolsWidth,value:280
    SET=key:BRNWidth,value:280
END-ONLOAD

   
ReplyQuote
(@rtruss)
Trusted Member Registered
Joined: 4 years ago
Posts: 74
 

it would appear that i too need to read the updated docs as the new 3.13.2 (I am on 3.10.2) has made some changes and now things are missing ;).

BEGIN-ONLOAD overall seems to still be working regards to scale so that is awesome.

what is not working appears to be all my control items. Like this one.

CONTROL=wide:1,left:%HNLeft%,font-size:%ControlFontSize%,button-color:%blue%,display:Goto Helpnow,uri: https://helpnow.companyname.com

   
ReplyQuote
(@tof0006)
Active Member Registered
Joined: 4 months ago
Posts: 3
Topic starter  

Thanks a lot for your reply. I'm gonna test this right now.


   
ReplyQuote
Glenn
(@glenn)
Member Admin
Joined: 6 years ago
Posts: 1300
 

@rtruss add width and height options.


   
ReplyQuote
(@rtruss)
Trusted Member Registered
Joined: 4 years ago
Posts: 74
 

@glenn

So, what has changed since 3.10 to require that?

How well does it scale when using those settings?

I compared the pdf from both versions and there is no difference within the CONTROL sections of the doc to indicate this. 

The code I pasted previously works perfectly on 3.10.2.4365.


   
ReplyQuote
(@rtruss)
Trusted Member Registered
Joined: 4 years ago
Posts: 74
 

OK, so I added a variable for width and height for my control items and still nothing.  I think you have a bug with the newer version and how it processes the ONLOAD items with this 3.13 version. I can only see stuff if I 'hard code' the width and height options as some already had variables for width and still not showing up.  Oddly enough the font-size, left and button color variables seem to work but not actual button sizing. 

 

I attached a scrubbed version of the ini file from my device, if anyone wants to confirm a bug with it.  I use powershell to tailor the config based on mfg and if it's a server or not.


   
ReplyQuote
(@rtruss)
Trusted Member Registered
Joined: 4 years ago
Posts: 74
 

Is hide-no-result not working either, at least for a CMD= item?

 

I have neither a reboot or updates but the text is still showing up, other items seem to be working but just not these 2.

# Pending Reboot

CMD=file:powershell.exe,parameters:-executionpolicy remotesigned -noprofile -file .\pending-reboot.ps1 ,interval:3600,font-size:120%,color:%Red%,font-face:Tahoma,text:Reboot Pending,no-wait:2,hide-no-result:1

# Windows Updates
CMD=file:powershell.exe,parameters:-executionpolicy remotesigned -noprofile -file .\windows-updates.ps1 ,interval:3600,font-size:120%,color:%Red%,font-face:Tahoma,text:Updates Pending,no-wait:2,hide-no-result:1

 


   
ReplyQuote
Glenn
(@glenn)
Member Admin
Joined: 6 years ago
Posts: 1300
 

Posted by: @rtruss

@glenn

So, what has changed since 3.10 to require that?

How well does it scale when using those settings?

I compared the pdf from both versions and there is no difference within the CONTROL sections of the doc to indicate this. 

The code I pasted previously works perfectly on 3.10.2.4365.

The absolute positioning paradigm is responsible.  Lots of code changes to support it, most good but sometimes unexpected side effects.

Edit: *and* extensive work to support Windows scaling.  In other words there's been a metric tonne of code changes since 3.10

 


   
ReplyQuote
Glenn
(@glenn)
Member Admin
Joined: 6 years ago
Posts: 1300
 

Posted by: @rtruss

OK, so I added a variable for width and height for my control items and still nothing.  I think you have a bug with the newer version and how it processes the ONLOAD items with this 3.13 version. I can only see stuff if I 'hard code' the width and height options as some already had variables for width and still not showing up.  Oddly enough the font-size, left and button color variables seem to work but not actual button sizing. 

 

I attached a scrubbed version of the ini file from my device, if anyone wants to confirm a bug with it.  I use powershell to tailor the config based on mfg and if it's a server or not.

I found an AV when the width option references a variable.

 


   
ReplyQuote
Glenn
(@glenn)
Member Admin
Joined: 6 years ago
Posts: 1300
 

Posted by: @rtruss

Is hide-no-result not working either, at least for a CMD= item?

 

I have neither a reboot or updates but the text is still showing up, other items seem to be working but just not these 2.

# Pending Reboot

CMD=file:powershell.exe,parameters:-executionpolicy remotesigned -noprofile -file .\pending-reboot.ps1 ,interval:3600,font-size:120%,color:%Red%,font-face:Tahoma,text:Reboot Pending,no-wait:2,hide-no-result:1

 

# Windows Updates
CMD=file:powershell.exe,parameters:-executionpolicy remotesigned -noprofile -file .\windows-updates.ps1 ,interval:3600,font-size:120%,color:%Red%,font-face:Tahoma,text:Updates Pending,no-wait:2,hide-no-result:1

 

That has always been the case, CMD always returns a result regardless of the outcome of the command itself.

 


   
ReplyQuote
Glenn's Page