GrafX2 overwrites colours in the palette with its default UI colours when loading a file

[GoogleCodeExporter]

What steps will reproduce the problem?

Not known exactly, but happens when loading a BMP.

What do you see?

When loading an 8 bit BMP (created with GrafX2), often one or two colours in 
palette are replaced with either 180,180,180 or 87,98,122. These are the GUI 
colours in the default palette. The colour indices overwritten are always in 
the last 16, often 255, or 254&255, or the last 1 or 2 blacks in the palette. 
Behaviour seems to be always the same for the same file.

What version of GrafX2 are you using? On what operating system?

Occurs both in a build of the latest SVN revision, and the last release, on 
both Windows and Linux.

Is this a known problem? It's driving me crazy! If not, I'm more than happy to 
dive into the source tomorrow and find out what's going on.

Example is attached. The colour 255 is 180,180,180 (because the original was 
overwritten!), but loading it in GrafX2, colour 255 becomes 87,98,122.

Original issue reported on code.google.com by TeeEm...@gmail.com on 5 Mar 2012 at 12:05

Attachments:

• concrete_tops2.bmp

[GoogleCodeExporter]

You can disable this behavior in the Settings : It's in the first page, "Safety 
colors". When the setting is 'YES', Grafx2 selects up to 4 unused colors and 
stores the ideal menus colors there. (A color is deemed unused if no pixel has 
this color)
If you set it to NO, Grafx2 will stop modifying your image's palettes.

The default setting is YES as a safety, because if you opened an image with a 
fully black palette for example, the Grafx2 menus would become invisible and 
unusable. In this case, it's useful to know that in the palette screen (press P 
to enter it) you can always press Backspace to force the menu colors.

Original comment by yrizoud on 5 Mar 2012 at 7:19

• Changed state: Solved
• Added labels: OpSys-All
• Removed labels: OpSys-