News:

The new Release 25.03 is out! You can download binaries for Windows and many major Linux distros here .

Main Menu

Some annoying symbols-browser issues

Started by Jenna, August 01, 2011, 10:20:29 PM

Previous topic - Next topic

Loaden

Quote from: jens on August 02, 2011, 11:09:33 PM
The attached patch seems to fix the event-handler issue and should not break anything other.
Can you please test it ?
It's works. But why? It's wxWidgets's bug?

ollydbg

Quote from: Loaden on August 03, 2011, 03:43:06 AM
Quote from: jens on August 02, 2011, 11:09:33 PM
The attached patch seems to fix the event-handler issue and should not break anything other.
Can you please test it ?
It's works. But why? It's wxWidgets's bug?
I have the same question hare, the patches seems only convert the event-handler map from static macro definition to dynamically linked style, are there much difference on propagate messages? I guess it is a bug in Linux version of wxWidgets. :D
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

MortenMacFly

Quote from: Loaden on August 03, 2011, 03:43:06 AM
It's works. But why? It's wxWidgets's bug?

Quote from: ollydbg on August 03, 2011, 05:39:56 AM
I have the same question hare, the patches seems only convert the event-handler map from static macro definition to dynamically linked style, are there much difference on propagate messages?

It's not a bug, but a matter of ordering the event handling. In fact, the wx guys really encourage to use this method (see here: http://wxwidgets.blogspot.com/2007/01/in-praise-of-connect.html). I am using it all the time in my personal projects and once you get used to it it's really quite handy. Especially the ability to switch the event propagation temporarily off for certain reasons is nice.


So I think we can safely apply Jens' patch.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

ollydbg

Quote from: MortenMacFly on August 03, 2011, 07:04:01 AM
Quote from: Loaden on August 03, 2011, 03:43:06 AM
It's works. But why? It's wxWidgets's bug?

Quote from: ollydbg on August 03, 2011, 05:39:56 AM
I have the same question hare, the patches seems only convert the event-handler map from static macro definition to dynamically linked style, are there much difference on propagate messages?

It's not a bug, but a matter of ordering the event handling. In fact, the wx guys really encourage to use this method (see here: http://wxwidgets.blogspot.com/2007/01/in-praise-of-connect.html). I am using it all the time in my personal projects and once you get used to it it's really quite handy. Especially the ability to switch the event propagation temporarily off for certain reasons is nice.


So I think we can safely apply Jens' patch.
Jens' patch indeed solve the problem, but I still believe its a bug in wx, because there is no reason that the event_table way does not work. (although wx guys use/suggest dynamical way, but the static event_table way should always work), and looking at c::b's source, there are many event_table usages. :D
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Loaden

Quote from: ollydbg on August 03, 2011, 07:13:57 AM
Jens' patch indeed solve the problem, but I still believe its a bug in wx, because there is no reason that the event_table way does not work. (although wx guys use/suggest dynamical way, but the static event_table way should always work), and looking at c::b's source, there are many event_table usages. :D
I have the same point!

MortenMacFly

Quote from: Loaden on August 03, 2011, 07:18:03 AM
I have the same point!
That might be true, but in fact you are doing 2 different things here. But I guess the wx guys can explain better - why not asking in the wx forums?
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

Loaden

Quote from: MortenMacFly on August 03, 2011, 07:20:13 AM
Quote from: Loaden on August 03, 2011, 07:18:03 AM
I have the same point!
That might be true, but in fact you are doing 2 different things here. But I guess the wx guys can explain better - why not asking in the wx forums?
I think I can't. Because my poor English. I can't explain this clear.
:D

MortenMacFly

#22
Quote from: Loaden on August 03, 2011, 07:24:36 AM
I think I can't. Because my poor English. I can't explain this clear.
And I just realised that for some obscure reason the wx shadownet forum seems gone?! Have they moved to a new place and I didn't get it? :shock:

EDIT: And what the hell is this:
http://forum.wxwidgets.org/
???
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

ollydbg

Quote from: MortenMacFly on August 03, 2011, 07:26:17 AM
Quote from: Loaden on August 03, 2011, 07:24:36 AM
I think I can't. Because my poor English. I can't explain this clear.
And I just realised that for some obscure reason the wx shadownet forum seems gone?! Have they moved to a new place and I didn't get it? :shock:

EDIT: And what the hell is this:
http://forum.wxwidgets.org/
???
The movement takes several days ago. :D, and the old domain name was expired, at that time, the wx forum has encountered a crash and recovery. (I'm subscribed to the wx-maillist under my thunderbird).
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

danselmi

Quote from: MortenMacFly on August 03, 2011, 07:26:17 AM
Quote from: Loaden on August 03, 2011, 07:24:36 AM
I think I can't. Because my poor English. I can't explain this clear.
And I just realised that for some obscure reason the wx shadownet forum seems gone?! Have they moved to a new place and I didn't get it? :shock:

EDIT: And what the hell is this:
http://forum.wxwidgets.org/
???
that's the wrong link. The right one is http://forums.wxwidgets.org.
spell checker plugin: [url="http://developer.berlios.de/projects/spellchecker/"]http://developer.berlios.de/projects/spellchecker/[/url]
nassi shneiderman plugin: [url="http://developer.berlios.de/projects/nassiplugin"]http://developer.berlios.de/projects/nassiplugin[/url]

MortenMacFly

Quote from: danselmi on August 03, 2011, 07:51:47 AM
that's the wrong link. The right one is http://forums.wxwidgets.org.
Darn! The missing "s" leads to this strange page...?! WTF?! :?
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]