Re: Tasking and wxWidgets

Lucretia wrote:
> 2) I could also go the other way and inside the
> wx.Base.Object.Object_Type (wxObject) provide a mutex object, such
> that every call in wxAda would lock (on entry) and unlock (on exit)
> thus providing thread safety if that particular object were accessed
> via multiple tasks. The overhead of constructing/destructing a mutex
> locker object, locking/unlocking the mutex object on every call would
> be rather high and thus, would most probably slow the application
> down to a crawl (although, not tested). Use of inlining might make
> this nicer?

Is the different between a response in 0.1 seconds and 0.15 seconds
particularly noticable with a GUI? I'm guessing at the actual times but
surely they are going to be very small (to the human eye), no?...

Could you provide the locking as an option at compile time? I.e. have 2
packages that providing locking but one is "begin null end;" (or "is null;"
for Ada2005, yes?) for everything.

Cheers

-- Martin


.