This topic contains 3 replies, has 3 voices, and was last updated by 
Cole Chapman
2 years, 7 months ago.
-
Posts
-
Hi,
Ted2 or maybe it’s Monkey2 (v- 1.0.0) will steal the mouse button input (Kernel/Desktop wide) when the debug built application has a ‘Concurrent list modification’ error (DebugAssert( _seq=_list._seq,”Concurrent list modification” ) – in list line 140). I’ve not been able to find a specific reason for the error but when it occurs I lose any mouse input as far as buttons go OS wide. The only way to get mouse button input back is to kill the compiled application. The same application built in release mode functions with no issues.
The debug built application will function fine until I click on the canvas area within the window. When I do it fails and generates a ‘Concurrent list modification’ error as the only output in console. I can move and resize the debug built application window and interact with other non-monkey applications/windows with no issues.
I’m using Linux Mint 17.2. I hope this is not to cryptic and I guess just FYI. I’m working on finding out why this occurs but loosing mouse button input on an error in debug feels like a issue beyond the scope of my applications code.
As a side note if you can add a code view to the list box in Ted2 I would use it by default. I’m old school and Ted2’s minimal style suits me nicely.
(Debian-Jessie) Ted2 will do the same for me if mx2cc returns an error and then I have to select the window again to regain input. But what’s worse is if I hit Open.. or Save.. then the requester opens and I get locked out of everything and have to restart my PC.
Anyone else have this problem?
Just commited some changes that might fix some of these issues.
The basic problem appears to be that SDL_CaptureMouse on linux gets a bit carried away!
That did the trick. Thanks Mark! I closed the github issue for it.
You must be logged in to reply to this topic.