changing auotmatic scaling of an grayscale image to user chosen limits seem to give the same (and wrong) scale.
The problem exist in the RC5 version for win32 (at least).
I have not checked if the same problem exist for the color modes.
This is really a bug. In fact it appears oon computers where the regional settings are different from English/American and fractions are after the comma and not the dot.
This needs to be fixed for international users !
Here is a detailed description of the bug from Henning :
Regarding the "bug" I reported yesterday - I have now found the origin of it. The feature I described was observed on Erik Mejdals PC. Since you closed the bug this morning I tested it on my PC and I was not able to reproduce it either. But the problem is the regional settings. Erik has the Danish turned on that means a comma is a , not a .
And with automatic scaling it had min 88.0 max 123.343 - if we remove the auto scaling and update these are read as 880 and 123343 which is quite different. If we changed the dot to a comma min 88,0 and 123,343 we got the correct scaling.
Can we make ImageViewer java(eclipse) use the regional settings when it fills in the entries. I the automatic scaling had written YY,XXX instead XX.YYY in the entries it would be apparent for the user how the values are interpreted.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just a remark - This bug actually also gives problems if a zoom area is made, since the scale in the zoom enherits the min/max from parent image, i.e. no autoscale. Since the numbers are but in as XXXX.YYY it is read as XXXXYYY leading to dark zoom.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Cannot reproduce this bug. Please open it if you think it is not fixed and explain the effects of the bug more precisely.
This is really a bug. In fact it appears oon computers where the regional settings are different from English/American and fractions are after the comma and not the dot.
This needs to be fixed for international users !
Here is a detailed description of the bug from Henning :
Regarding the "bug" I reported yesterday - I have now found the origin of it. The feature I described was observed on Erik Mejdals PC. Since you closed the bug this morning I tested it on my PC and I was not able to reproduce it either. But the problem is the regional settings. Erik has the Danish turned on that means a comma is a , not a .
And with automatic scaling it had min 88.0 max 123.343 - if we remove the auto scaling and update these are read as 880 and 123343 which is quite different. If we changed the dot to a comma min 88,0 and 123,343 we got the correct scaling.
Can we make ImageViewer java(eclipse) use the regional settings when it fills in the entries. I the automatic scaling had written YY,XXX instead XX.YYY in the entries it would be apparent for the user how the values are interpreted.
Just a remark - This bug actually also gives problems if a zoom area is made, since the scale in the zoom enherits the min/max from parent image, i.e. no autoscale. Since the numbers are but in as XXXX.YYY it is read as XXXXYYY leading to dark zoom.