scenarios, so they should both be possible.
> >>
> >
> > This may be so, but given the implementation as it is in Delphi,
> > hopefully you can now understand my problem with the Lazarus
> > exception dialog :-)
> >
> >
> Yes, and no:
>
&g
>> - any other exception, that aborts the write, and transfers error
>> handling to the main loop
>>
>> There are usages for both scenarios, so they should both be possible.
>>
>
> This may be so, but given the implementation as it is in Delphi,
> ho
ch can be
> used to abort writing the data, but not defer error handling to the mainloop
> - any other exception, that aborts the write, and transfers error
> handling to the main loop
>
> There are usages for both scenarios, so they should both be possible.
This ma
Graeme Geldenhuys wrote:
> Please note, I don't use db-aware components, but here follows the
> help from Kylix 3.
>
> On Tue, Mar 17, 2009 at 3:46 PM, Martin Friebe wrote:
>
>> I have to admit, I have limited knowledge of the exact details of the
>> data-aware components, and rather was making
Martin Friebe schrieb:
> If a component throws an exception outside any call from your code
> (which you can place in a "try except end"), a place like OnDataReceived
> which is triggered automatically, then this component has a bug (IMHO).
ACK. Asynchronous operations never should throw excep
Michael Van Canneyt schrieb:
> In the OnValidate event of a TField, you are supposed to throw an exception
> to stop the user from entering wrong data in the field. This exception can
> only be caught by the program event loop. This is so by design, and the
> recommended way by Borland.
Even Bo
On Tue, Mar 17, 2009 at 3:46 PM, Martin Friebe wrote:
> Anyway, the point is, if we are looking at the original source of the
> discussion (the build-in exception dialog) => that is at best the most
> limited case of handling an exception (It is simply displaying it). It
> does not check any need
Please note, I don't use db-aware components, but here follows the
help from Kylix 3.
On Tue, Mar 17, 2009 at 3:46 PM, Martin Friebe wrote:
>
> I have to admit, I have limited knowledge of the exact details of the
> data-aware components, and rather was making a general case about my
> perception
Michael Van Canneyt wrote:
>> If a component throws an exception outside any call from your code
>> (which you can place in a "try except end"), a place like OnDataReceived
>> which is triggered automatically, then this component has a bug (IMHO).
>> The component *should* have something like an
On Tue, 17 Mar 2009, Martin Friebe wrote:
> Michael Van Canneyt wrote:
> > On Mon, 16 Mar 2009, Hans-Peter Diettrich wrote:
>
> "In a GUI application, you rely on the program's event loop"
> Well, in my very personal opinion: This is just a bad design idea. If I
> throw an exception, I wr
On Tue, 17 Mar 2009, Martin Friebe wrote:
> Luca Olivetti wrote:
> > En/na Hans-Peter Diettrich ha escrit:
> >
> >
> >> Insert your exception handler in an more appropriate place, depending on
> >> the concrete application. The user can expect a diagnosis of what went
> >> wrong, and a chan
Luca Olivetti wrote:
> En/na Hans-Peter Diettrich ha escrit:
>
>
>> Insert your exception handler in an more appropriate place, depending on
>> the concrete application. The user can expect a diagnosis of what went
>> wrong, and a chance for correcting his preceding input.
>>
>
> For data
An exception is indeed a very valid thing, that can and maybe should
occur within many applications. But any exception should have some code,
that handles it.
And this handling code should not be the build-in Lazarus-exception
dialog. Because the build-in dialog does not know what the excepti
Michael Van Canneyt schrieb:
>> An unhandled exception IMO is due to some software bug, which the user
>> cannot cure in any way.
>
> That's a very restrictive definition of exception. An exception is
> a way to stop the normal logic and flow of the program.
ACK. And try-except clauses are the
On Tue, Mar 17, 2009 at 10:38 AM, Michael Van Canneyt
wrote:
>
> Borland explains this use in detail in chapter 14 of the Delphi 7
> manual.
Or chapter 13 in the Kylix 3 Developers Guide. ;-)
[...at least I still have one use for Kylix... It's help files and
documentation.]
Regards,
- Graeme
Michael Van Canneyt wrote:
>
> On Mon, 16 Mar 2009, Hans-Peter Diettrich wrote:
>
>> Michael Van Canneyt schrieb:
>>
>>> Is there a reason why the default exception dialog has a cancel
>>> button to kill the application ?
>> An unhandled exception IMO is due to some software bug, which the user
On Mon, 16 Mar 2009, Hans-Peter Diettrich wrote:
> Michael Van Canneyt schrieb:
>
> > Is there a reason why the default exception dialog has a cancel
> > button to kill the application ?
>
> An unhandled exception IMO is due to some software bug, which the user
> cannot cure in any way.
Tha
En/na Hans-Peter Diettrich ha escrit:
>
> Insert your exception handler in an more appropriate place, depending on
> the concrete application. The user can expect a diagnosis of what went
> wrong, and a chance for correcting his preceding input.
For data aware components (and probably for othe
Michael Van Canneyt schrieb:
> Is there a reason why the default exception dialog has a cancel
> button to kill the application ?
An unhandled exception IMO is due to some software bug, which the user
cannot cure in any way.
> We often use an exception to signal wrong entry of data or so,
> b
On Mon, Mar 16, 2009 at 23:44, Paul Ishenin wrote:
> Michael Van Canneyt wrote:
>> Is there a reason why the default exception dialog has a cancel
>> button to kill the application ?
>>
>> We often use an exception to signal wrong entry of data or so,
>> because it stops all further processing.
>>
Michael Van Canneyt пишет:
> Hello,
>
> Is there a reason why the default exception dialog has a cancel
> button to kill the application ?
>
> We often use an exception to signal wrong entry of data or so,
> because it stops all further processing.
>
> If the user then uses the cancel button,
On Mon, 16 Mar 2009, Samuel Herzog wrote:
> > Oh, good point to discuss about the use of exceptions.
>
> I use exceptions only for really "unexpected" things.
Well, Borland introduced specially the 'Abort' exception to
let the programmer 'jump out' of routines in case of need.
It's never show
de my code.
e.g.
try
FExcel := GetActiveOleObject('Excel.Application');
except
//do something
end;
Von: Michael Van Canneyt
An: Lazarus mailing list
Gesendet: Montag, den 16. März 2009, 14:14:56 Uhr
Betreff: [Lazarus] Exception dialog
On Mon, Mar 16, 2009 at 3:14 PM, Michael Van Canneyt
wrote:
>
> Is there a reason why the default exception dialog has a cancel
> button to kill the application ?
I have been wondering that for 5 years (since I moved from Delphi),
but was to shy to ask. ;-)
Regards,
- Graeme -
_
Michael Van Canneyt wrote:
> Is there a reason why the default exception dialog has a cancel
> button to kill the application ?
>
> We often use an exception to signal wrong entry of data or so,
> because it stops all further processing.
>
> If the user then uses the cancel button, the program is
Hello,
Is there a reason why the default exception dialog has a cancel
button to kill the application ?
We often use an exception to signal wrong entry of data or so,
because it stops all further processing.
If the user then uses the cancel button, the program is simply
ended, which is not wh
26 matches
Mail list logo
