wxWidgets Discussion Forum

Оживляем тему? :-) wxSocketBase::Close void Close() (1) ...Upon socket destruction, Close is automatically called... Remark/Warning (2) Although Close immediately disables events for the socket, it is possible that event messages may be waiting in the application's event queue. The application must ...

Hmm, you know, I was curious and have tested it a bit myself on Windows with wxWidgets 2.8.9. And indeed after leftup event the window receives motion event, and it comes from the OS (WM_MOUSEMOVE). That is interesting. I'm not sure if this is how it should be, right now I have another test in mind ...

AFAIK, you won't catch AV just like that. For this you'll have to use either MS-specific __try and friends or enable those exceptions in project settings (/EHa switch). In VC++2008 Express this is done under 'Configuration Properties->C/C++->Code Generation->Enable C++ Exceptions'. This is not wx pr...

Well, maybe it indeed doesn't matter, but I too have this checkbox set

Thanks for the explanation, I got it now.

I'd better check what I would get with different browsers (currently I use Google Chrome), maybe this'll get me additional input on this.

Hello, I've noticed this strange thing: if I log in on the forum, click on 'View posts since last visit' I see those posts well good. But if I close the browser and then log in again, I: 1. See only new posts that were made after me logging off (which is pretty understandable - they're indeed 'since...

There's not much need in reproducing, it's all pretty imaginable. The double click is a sequence of two clicks, and a click is a sequence of two events: mouse goes down then up. Double click may be registered as a click + mouse down event. And of course some time passes between those events. When su...

About part 1 and scrollbars, well, without any code snippets it'd be really hard to diagnose just something. For part 2 - there are things like mouse resolution and tracking rate, and also how OS 'speaks' with the mouse. To be short, mouse updates are done in some (small) time intervals, and if the ...

Oh, I see your point now. Well, AFAIK, you can do just fine with events/WaitOnConnect(), though now you've confused me and I'm in a little doubt

Actually the socket's Destroy() method calls Notify(false) thus suppressing notifying the handler. I've seen the complains about some troubles related to the order of deletion of socket/handler but I suspect the reason for them is something different than event occurring after Destroy() call.

I don't get it... What do you mean by 'direct' connect? If you called non-blocking Connect() ('wait' parameter is false), then you will receive one of the events depending on the result, event if the connection establishes as would seem 'just in the moment of Connect() call' (though it'd be asynchro...

Hello Nathan,

Try wxEVT_ERASE_BACKGROUND and this function.

Hello,

For the device id you could check one of those posts:

http://msdn.microsoft.com/en-us/library/aa909165.aspx
http://msdn.microsoft.com/en-us/library/aa446562.aspx

One of them is actually for the .NET, but I don't see real trouble adapting it to C++.

As for SD card, you can try this

I suggest you start with this tutorial , it could help you quite a lot. No offense, but it's just so well not right starting on big things like wxWidgets without understanding simple things about the language itself. Now I know this forum is made to help people solve problems, but that's it. I think...

Can you describe what wxWidgets version you're using and how exactly did you determine those leaks?