On 12/06/2012 09:06 AM, Reinier Olislagers wrote:
On 6-12-2012 14:58, Andrew Brunner wrote:
On 12/05/2012 10:28 PM, Hans-Peter Diettrich wrote:
How wide would that row be, at say 120 dpi? <BG>
This is not relevant to the issue at hand. As I stated before, the
progressbar component of the host operating system scales the
Min/Max/Position values and converts it to the client area of the
aggregate value.
So basically, with the Progressbar on 64bit systems the current progress
bar won't accept values except longint. This is a flaw. This must be a
64bit position. Otherwise this Lazarus component is relegated to the
least common denominator of 32bit oses.but I
If I understand correctly what you're saying and *if* the OS requires a
64 bit number, then the Lazarus LCL code must be changed to scale the 32
bit integers given to it by the code/LFM streamed properties to 64 bit
integers.
This will maintain compatibility between projects. You may not care
about having your projects compile on multiple platforms without (too
many) code changes, but I and others do.
--
_______________________________________________
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
I just got into this thread, but I have been using Delphi since Version
1 (and Turbo Pascal back to Version 1 before that). Imo the Min, Max and
Pos parameters should all be set to the largest integer data type of the
underlying OS. If this is done, the scaling issue should be taken care
of automatically. There may be a latent flaw due to streaming of these
parameters, however.
Don Ziesig
--
_______________________________________________
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
