Desktop Info v3.21....
 
Notifications
Clear all

We appreciate the contributions many of you have been able to make towards repairing the storm damage and keeping a roof over our heads. With your help we’ve been able to complete much of the critical work. There is still work to be done to secure the house and your continued support will be a huge help.

Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.

Desktop Info v3.21.0

3 Posts
2 Users
0 Reactions
1,940 Views
Glenn
(@glenn)
Member Admin
Joined: 8 years ago
Posts: 1926
Topic starter  

Version 3.21.0

September 2025

Change 1: Added a Windows Service option. There is a sample service config file at sample-config\desktopinfo-service.ini.

Change 2: Fixed bug where an IF item may fail to switch off a button.

Change 3: The COLLECTOR item now retrieves both raw and formatted display data.


   
Quote
(@ndfan77)
New Member Registered
Joined: 6 months ago
Posts: 1
 

Hello,

Many thanks for the awesome app (just started using it after many years of bginfo).  Will send some coffee money shortly.

I think I've run into a small number formatting issue in 3.21.0.4966.  If I use the following item definition:

LOGICALDRIVES=interval:60,diskio:1,font-size:85%,text-align:l,\
  alarms:(%7 ge 90 0070f0),\
  row-text:,display:Drive %1: %7[2.1f]%\, %8[1.0B] Free

The resulting output is (also attached):

<snipped>
Drive C: 37.4%, 171G Free
Drive D: 0.1%, 275G Free

The manual indicates the floating point type (%7[2.1f]) should pad on the left with zeros.  So shouldn't the output instead be(?):

<snipped>
Drive C: 37.4%, 171G Free
Drive D: 00.1%, 275G Free

 Thanks again,

-ndfan77

P.S. It might also be useful if we could right justify number formats with leading spaces... 

 

This post was modified 6 months ago by ndfan77

   
ReplyQuote
Glenn
(@glenn)
Member Admin
Joined: 8 years ago
Posts: 1926
Topic starter  

Posted by: @ndfan77

The manual indicates the floating point type (%7[2.1f]) should pad on the left with zeros.  So shouldn't the output instead be(?):

I think you've misread the manual unless you found a typo.  On page 53, it states:

The four general number types are:
d decimal w = minimum width left padded with zeros, p=not used
f float w = minimum width left padded with spaces, p=decimal places
n float same as 'f', commas inserted for thousands
x hexadecimal w = minimum width left padded with zeros, p=not used

Where it refers to the width, that means the total width of the output including the decimal point and any digits following that. In your example, it states the total width should be at least 2 characters with one digit after the decimal place. If you wanted consistent output for a number that looks like "xx.x"  you would want a width of 4 with one digit after the decimal place,  or [4.1f].  This would left pad the output with spaces if the output is less than four characters wide.

Of course you've still got the issue of variable width fonts...


   
ReplyQuote
Glenn's Page