-
Bug
-
Resolution: Fixed
-
P5
-
17, 19
-
b26
-
generic
-
generic
Currently, the logging of the J2DBench differs from run to run. Each time the order of the parameters is different.
For example:
First run:
with to Default Frame, bounce, 1x1, SrcOver, ident, !extraalpha, !xormode, !clip, Default, from transvolimg translucent, !touchsrc, Nearest neighbor
Next run:
with SrcOver, bounce, Nearest neighbor, ident, !touchsrc, to CompatImage(Opaque), Default, 1x1, !xormode, !clip, from bmcompatimg bitmask, !extraalpha
The root cause is that the options are stored in the Hashtable and printed in the "random" order.
For example:
First run:
with to Default Frame, bounce, 1x1, SrcOver, ident, !extraalpha, !xormode, !clip, Default, from transvolimg translucent, !touchsrc, Nearest neighbor
Next run:
with SrcOver, bounce, Nearest neighbor, ident, !touchsrc, to CompatImage(Opaque), Default, 1x1, !xormode, !clip, from bmcompatimg bitmask, !extraalpha
The root cause is that the options are stored in the Hashtable and printed in the "random" order.