On 11/12/2012 17:55, Andrew Brunner wrote:
So the question becomes... Is the use of int64 actually ubiquitous on
a 32bit system? If so, it may stand to reason that the values of
Progress bar be expanded to Int64 even on 32bit systems.
http://bugs.freepascal.org/view.php?id=23471
I am *no
On 11/12/2012 17:55, Andrew Brunner wrote:
On 12/05/2012 01:48 PM, Andrew Brunner wrote:
I'm getting overflow exceptions on values greater than integer. Can
someone revise all values from integer to ptrint so on 64 bit systems
it will be valid.
Ok, I have a patch for the LCL but before we ge
On 12/05/2012 01:48 PM, Andrew Brunner wrote:
I'm getting overflow exceptions on values greater than integer. Can someone
revise all values from integer to ptrint so on 64 bit systems it will be valid.
Ok, I have a patch for the LCL but before we get further I think we need
more discussion o
On 12/7/12, Andrew Brunner wrote:
> But typically a progress bar is used in conjunction with streams. Therefore
> it should handle the same size as objects like that.
Why?
I typically set Max to 100 and calc percentage, et voila...
Bart
--
___
Lazar
On 7-12-2012 21:12, Andrew Brunner wrote:
>
> On Dec 6, 2012, at 8:57 AM, Donald Ziesig wrote:
>
>> 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 la
On Dec 6, 2012, at 8:57 AM, Donald Ziesig wrote:
> 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. I
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?
This is not relevant to the issue at hand. As I stated before, the
progressbar component of the host o
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?
>>
>>
>
> 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
On 12/05/2012 10:28 PM, Hans-Peter Diettrich wrote:
How wide would that row be, at say 120 dpi?
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 t
On Wed, Dec 5, 2012 at 10:56 PM, Andrew Brunner wrote:
> I assert that use of anything but ptrint in the factory with respect to
> tprogressbar is a flaw. And it's a quick fix.
It is not a flaw, you need to scale your number to fit the provided size.
--
Felipe Monteiro de Carvalho
--
___
On Thu, Dec 6, 2012 at 3:34 AM, Andrew Brunner wrote:
> In the time it took to convince you there is a problem the solution could
> have been adopted.
> Please this isn't about pixels, it's about efficient scaling onto 64bit
> systems. Hence a flaw.
I think the streaming issues will turn down
On 2012-12-06 04:42, Hans-Peter Diettrich wrote:
> A control on screen is painted pixel-by-pixel, you cannot have
> fractions of pixels on the screen.
Actually you can, but it is more of an optical illusion. :)
eg: floating point calculation for anti-aliased drawing. With AggPas I
can draw a 0.4
waldo kitty schrieb:
Integer has 2^31 positive values which should be enough for all the
positions shown in a graphical component.
Does anybody have an screen or printer, with so many pixels? ;-)
[That's why Integer is way enough for a progress bar]
multi-monitors spread horizontally??
How
Andrew Brunner schrieb:
Integer has 2^31 positive values which should be enough for all
the positions shown in a graphical component.
Does anybody have an screen or printer, with so many pixels? ;-)
[That's why Integer is way enough for a progress bar]
You are serious ?!? There is no corr
On Dec 5, 2012, at 4:43 PM, Hans-Peter Diettrich wrote:
> Juha Manninen schrieb:
>> On Wed, Dec 5, 2012 at 9:48 PM, Andrew Brunner wrote:
>>> I'm getting overflow exceptions on values greater than integer. Can
>>> someone revise all values from integer to ptrint so on 64 bit systems it
>>> w
On Thu, Dec 6, 2012 at 2:46 AM, waldo kitty wrote:
> multi-monitors spread horizontally??
C'mon...
Please take a calculator and check how much is 2^31.
Juha
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepas
On 12/5/2012 17:43, Hans-Peter Diettrich wrote:
Juha Manninen schrieb:
On Wed, Dec 5, 2012 at 9:48 PM, Andrew Brunner wrote:
I'm getting overflow exceptions on values greater than integer. Can someone
revise all values from integer to ptrint so on 64 bit systems it will be valid.
You can sca
Juha Manninen schrieb:
On Wed, Dec 5, 2012 at 9:48 PM, Andrew Brunner wrote:
I'm getting overflow exceptions on values greater than integer. Can someone
revise all values from integer to ptrint so on 64 bit systems it will be valid.
You can scale the value in your code before using it for P
On Dec 5, 2012, at 4:40 PM, Juha Manninen wrote:
> On Thu, Dec 6, 2012 at 12:19 AM, Andrew Brunner wrote:
>> The design time vales are all zeros anyways.
>
> ProgressBar.Position can be set also at design time.
>
>
Point 1. The IDE input could reject values beyond 2g. It probably does tha
On Thu, Dec 6, 2012 at 12:19 AM, Andrew Brunner wrote:
> The design time vales are all zeros anyways.
ProgressBar.Position can be set also at design time.
Juha
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freep
On Dec 5, 2012, at 4:01 PM, Vincent Snijders wrote:
> 2012/12/5 Andrew Brunner :
>> .
>>
>> On Dec 5, 2012, at 2:52 PM, Juha Manninen wrote:
>>
>>> On Wed, Dec 5, 2012 at 9:48 PM, Andrew Brunner
>>> wrote:
I'm getting overflow exceptions on values greater than integer. Can
someo
2012/12/5 Andrew Brunner :
> .
>
> On Dec 5, 2012, at 2:52 PM, Juha Manninen wrote:
>
>> On Wed, Dec 5, 2012 at 9:48 PM, Andrew Brunner wrote:
>>> I'm getting overflow exceptions on values greater than integer. Can
>>> someone revise all values from integer to ptrint so on 64 bit systems it
>>
.
On Dec 5, 2012, at 2:52 PM, Juha Manninen wrote:
> On Wed, Dec 5, 2012 at 9:48 PM, Andrew Brunner wrote:
>> I'm getting overflow exceptions on values greater than integer. Can someone
>> revise all values from integer to ptrint so on 64 bit systems it will be
>> valid.
>
> You can scale
On Wed, Dec 5, 2012 at 9:48 PM, Andrew Brunner wrote:
> I'm getting overflow exceptions on values greater than integer. Can someone
> revise all values from integer to ptrint so on 64 bit systems it will be
> valid.
You can scale the value in your code before using it for ProgressBar's Positio
I'm getting overflow exceptions on values greater than integer. Can someone
revise all values from integer to ptrint so on 64 bit systems it will be valid.
Thanks.
Andrew Brunner,
Aurawin LLC
512.574.6298
http://aurawin.com/
Aurawin is great new way to store and share your pictures, videos
25 matches
Mail list logo
