Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » Draw, Display, Images, Bitmaps, Icons » bug in ImageBuffer::Line() and operator[]
Re: bug in ImageBuffer::Line() and operator[] [message #15440 is a reply to message #15438] Wed, 23 April 2008 21:04 Go to previous message
mirek is currently offline  mirek
Messages: 13975
Registered: November 2005
Ultimate Member
nixnixnix wrote on Wed, 23 April 2008 13:18

I am getting the issue under Win32 and it doesn't appear to be related to calling Refresh as I get the same behaviour when I comment it out and I have many other functions which don't suffer from this bug although I will replace these calls with PostCallback() just to be sure.

Basically the Image object causes an ASSERT(data) even though the data object is perfectly valid.

Are threads other than the main thread allowed to make and refer to Image objects?



Yes. Anyway, as always with MT, if multiple threads work with single Image variable, you need to serialize access via Mutex.

Quote:


I don't really think I understand what you're telling me here. I am allowed to use PostCallback in threads other than the main right?



Yes, but ONLY PostCallback (and related event queue functions). Anything else in CtrlCore and beyond (-> CtrlLib, RichEdit... anything that includes CtrlCore) is disallowed.

(Draw, OTOH, you can use in multiple threads).

Mirek
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: problems drawing in Linux (ubuntu 7.10)
Next Topic: Bug: ImageBuffer::alpha not initialised on X11
Goto Forum:
  


Current Time: Fri May 03 15:27:51 CEST 2024

Total time taken to generate the page: 0.02836 seconds