Problem defining colors

[PHFiUser]

I'll be grateful if someone could help me on this. I'm opening the Color dialogue and I'm trying to define a color giving RGB values, e.g. 247 247 247. The problem is that Photo Filtre lets me write only the first two digits of each number. In the example above, Photo Filtre lets me write only 24 not 247. When I press "7" a sound comes from the PC (asterisk sound, as if I did something wrong) and number "7" is not written!

I'm using version 6.5.3 on Windows 8.

[Antonio]

in what color dialog ?
I think the value must be in hexa (2 digit)

247 is F7 in hexa

[PHFiUser]

I'm not sure I made myself clear. I know how to change colors, the problem is that PhotoFiltre won't let me write the numbers!

The color dialogue I'm referring to appears when one clicks on a large color square at the Tools Palette.

[Antonio]

I reply to your remark :

The problem is that PhotoFiltre lets me write only the first two digits of each number
==> in this cae enter the value in exa, not (247, 247, 247) but (F7, F7, F7)

Send me a screenshot of this dialog box with 2 digit to understand better

[PHFiUser]

Here is the image showing my problem. When I add a third number, PhotoFiltre refuses to accept it!

[Antonio]

did you tryed to enter "F7" for RGB value ?

[PHFiUser]

It doesn't do anything.

[Antonio]

I find it

"http://answers.microsoft.com/en-us/wind ... 6030822519"

[PHFiUser]

Ouaou! Since I always use PhotoFiltre I didn't notice that the problem is there in other applications too! As you found out, it is a problem with Windows, not with PhotoFiltre, perhaps I changed something that caused some damage!

Sorry for the trouble. If I find how the problem is solved I will post a message here in case someone else in the future needs an answer!

Thanks very much, and congratulation for PhotoFiltre!

[Antonio]

This color dialog is a native windows color and applications can use it.

I use windows 7 too without this bug, perhaps an windows update bugged ?
I think microsoft will fixe it...

[PHFiUser]

It was a Windows update problem. After a recent update the problem disappeared.

Thanks again!