Re: (forte-users) PurgeEvents doesn't

Question

Dear Duncan,
I think it would be easier to set the State attribute of your button widget to
FS_INVISIBLE or FS_VIEW in the part where you are handling the click event.
See the attached .pex file file it contains a simple test program which consists of
two window the first has a start and a stop button, but stop button is invisible
till you press the start button. The start button starts the second window as a
separate task and the start button becomes invisible, the stop button visible. In
this way you can assure that the user can only start one task and not more.
Best Regards,
Tamas Deak
Duncan Kinnear wrote:
Hi folks!
Really, the subject line says it all!
I'm calling Window.PurgeEvents() and can watch the Event Queue in the
debugger not changing in the slightest.
We are trying to start a seperate task from a button but we do not want
the user to be able to start more than one task. They can at this stage
by double clicking on the button.The event stack stores the second
click and executes it when the task is finished.
Cheers,
Duncan Kinnear,
McCarthy and Associates, Email: [email protected]
PO Box 764, McLean Towers, Phone: [phone]
Shakespeare Road, Napier, New Zealand. Fax: [phone]
Providing Integrated Software to the Meat Processing Industry for over 10 years
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]
Tamas Deak
Lufthansa Systems Hungary
(forte developer)
2-6 Mazsa ter, Budapest, 1107, HUNGARY
(36-1) 4312 973
[email protected]
[email protected][email protected]-

Answer 1

Hi Jorge,
Instead of using
Data.SetValue(FormatDouble.DecodeDouble(self.PKg));
use
Data.SetValue(FormatDouble.DecodeDecimal(self.PKg,Data.Scale)); //
This will take the second parameter of scale
You will see the desired results.
Thks,
Sanjay
-----Original Message-----
From: Dave Ortman [SMTP:dortmanyahoo.com]
Sent: Monday, March 05, 2001 12:32
To: Jorge Bellido; forte-userslists.xpedior.com
Subject: Re: (forte-users) I don't understand why appear new
decimals.
Simply put, the problem stems from the fact that
floating-point arithmetic is inherently imprecise.
Rounding errors are common.
With doubles, you get 16 digits of accuracy. Beyond
that there is no guarantee.
If you want more information:
http://docs.sun.com/htmlcoll/coll.648.2/iso-8859-1/NUMCOMPGD/ncg_goldberg.ht
ml
-Dave Ortman
--- Jorge Bellido <jorge.bellidoeam.es> wrote:
> I have another problem with numbers. So,
>
> Data: DecimalNullable = new;
> Data.Scale = 20;
> FormatDouble.Template = TextData(value='#');
>
> Dato.SetValue(FormatDouble.DecodeDouble(self.PKg));
>
> PKg is a widget DataField, whose mapped type is
> TextData with input mask float. When I write 1.12
> into the widget the variable Data is
> 1.1200000000000001, and I can't understand it. I
> would like that variable Data was 1.12.
>
> Could anybody to explain it?
>
> Thank you very much.
>
For the archives, go to: http://lists.xpedior.com/forte-users and
use
the login: forte and the password: archive. To unsubscribe, send in
a new
email the word: 'Unsubscribe' to:
forte-users-requestlists.xpedior.com