| | [ Return to Bugs & Features | Roadmap 1.3 | SVN ⇄ GIT ]
STR #2817
| Application: | FLTK Library |
|---|
| Status: | 1 - Closed w/Resolution |
|---|
| Priority: | 1 - Request for Enhancement, e.g. asking for a feature |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | Core Library |
|---|
| Summary: | Add a hook to track timeouts |
|---|
| Version: | 1.3-feature |
|---|
| Created By: | mingodad |
|---|
| Assigned To: | matt |
|---|
| Fix Version: | None |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
Trouble Report Comments:
| |
| #1 | mingodad
13:35 Mar 29, 2012 |
| Here is a patch to add a hook to track timeouts the main reason to implement it for me is to catch exceptions on win32 with mingw.
It is in the same line of the Fl::handle hook.
ex:
Fl::do_call_timeout_ = &my_do_call_timeouts;
void my_do_call_timeouts(Fl_Timeout_Handler th, void *data){
try {
(*th)(data);
}
catch(DBException &e)
{
fl_alert(e.what());
}
} | |
| |
| #2 | matt
13:09 Feb 02, 2019 |
| Sorry, but what you are doing is easily implemented by moving the try .. catch block into the timeout itself. This feature does not solve a common problem, but is very specific for your approach. I'll have to reject this. | |
[ Return to Bugs & Features ]
|
| |
