[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Thread-safe access to graphic objects - proposal
From: |
Maciek Gajewski |
Subject: |
Re: Thread-safe access to graphic objects - proposal |
Date: |
Fri, 4 Jul 2008 20:22:41 +0200 |
User-agent: |
KMail/1.9.9 |
Driss Ghaddab wrote
Event when properties are only read, they have to be protected by mutex, to
retain consistency ant to keep them from being deleted in another thread.
Maciek Gajewski
> To set an object property, there are four cases:
> - octave thread can set the value, but it needs to protect from mutual
> access (i.e. the GUI thread may modify the value, thus the mutex);
> - octave thread can set the value, but it does not need to protect from
> mutual access (i.e. the GUI thread never modifies that value)
> - octave thread is not allowed to modify the value and delegates the
> task to the GUI thread,
> - or, the property is read only and it is not allowed to modify it.