000080 > FFFF80 and other color mysteries

Things you’d like to miss in the future...
Forum rules
:warnred20: :warnred20: :warnred20: :warnred20: :warnred20: READ THIS AND DO IT!!! :warnred20: :warnred20: :warnred20: :warnred20: :warnred20:

:info: Please include the following information:
1) Your XYplorer Version (e.g., v28.00.0801)
2) Your Windows Version (e.g., Win 11)
3) Your Screen Scaling Percentage (e.g., 125%).

:info: We strongly recommend adding your Windows Version and Screen Scaling Percentage to the Location field in your Profile or to your Signature. That way, you only have to type them once, and we won't have to search for that vital information.

:info: When attaching an Image, please use the Attachment tab at the bottom of your post and click "Add files".

:warnred20: :warnred20: :warnred20: :warnred20: :warnred20: READ THIS AND DO IT!!! :warnred20: :warnred20: :warnred20: :warnred20: :warnred20:
Post Reply
pissant
Posts: 179
Joined: 05 Nov 2005 22:45

000080 > FFFF80 and other color mysteries

Post by pissant »

Just updated to 5.20.0000 from the previous beta.

I have a file type color specified as 000080 (RGB: 0/0/128). Whenever I set this color and close/restart XY, it reverts to the unbearable color FFFF80 instead.

I also have "/compressed" set to 0000FF (0/0/255), and while it remains correct in the INI file, when viewed in the color configuration area, it appears white (FFFFFF). XY is also applying FFFFFF to actual compressed file system objects, so obviously it's not using the 0000FF color from the INI.

j_c_hallgren
XY Blog Master
Posts: 5826
Joined: 02 Jan 2006 19:34
Location: So. Chatham MA/Clearwater FL
Contact:

Post by j_c_hallgren »

FYI: Basic problem already reported in "Color Filter Blues" thread by surrender, jacky, and myself.
http://www.xyplorer.com/xyfc/viewtopic.php?t=1049
Still spending WAY TOO much time here! But it's such a pleasure helping XY be a treasure!
(XP on laptop with touchpad and thus NO mouse!) Using latest beta vers when possible.

pissant
Posts: 179
Joined: 05 Nov 2005 22:45

Post by pissant »

Oops, damn me. I thought I checked for a similar post before blathering on needlessly. Thanks for the heads-up.

And with regard to this:
Gandolf wrote:
admin wrote:In case of INI file corruption at start up (e.g. because you
manually edited it and made a mistake), you'll now get a warning
message with a recommendation about how to proceed best to avoid any
loss of configuration settings.
But we don't get a message when the program corrupts the ini file!!
I want to say, since I am the one who prompted this change to begin with, that it was the program that corrupted the INI file in the first case as well. I've never manually edited my INI file. But anyway...

Post Reply