Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
wxExecute problems on first start...
MortenMacFly:
--- Quote from: jens on May 18, 2012, 01:48:22 pm ---I was just bitten by it the first time (after switching my OS to fedora).
I can just start building a second time and it works.
--- End quote ---
Same for me.
If I am very fast, this can be three times, too.
--- Quote from: jens on May 18, 2012, 01:48:22 pm ---I'm not sure, but it only seems to happen, if CC is still parsing. I will try if I can reproduce it.
--- End quote ---
Yes - this is definitely related (as I mentioned).
BTW: It seems no-one of the devs really cared so much about the internal report so far. Did you get no notification on that?
Jenna:
--- Quote from: MortenMacFly on May 18, 2012, 06:42:03 pm ---BTW: It seems no-one of the devs really cared so much about the internal report so far. Did you get no notification on that?
--- End quote ---
Which report do you mena ?
The posts in "Remember me" ?
I get notifications for each post in the forum, but not for these as far as I remember.
MortenMacFly:
--- Quote from: jens on May 19, 2012, 08:31:52 am ---Which report do you mena ?
The posts in "Remember me" ?
--- End quote ---
Yes, those I meant. :-)
Jenna:
I now get notified on new replies.
The cause is, that you only get notification mails for new topics or for topics you have posted in.
ollydbg:
--- Quote from: MortenMacFly on May 17, 2012, 04:23:43 pm ---
--- Quote from: Folco on May 17, 2012, 04:03:22 pm ---(Morten, your link seems to be dead)
--- End quote ---
For the record, this is our "task list":
--- Quote from: MortenMacFly ---Task:
- Fix an issue, that when having a workspace with many targets, macro manager in combination with CC does not work initially with global vars
* have a ws with many project - all relying on a global var, e.g. "wx"
* open the workspace
* quickly hit compile workspace to compile all which would need resolved #wx global vars
* -> error at the first wx include
* in the debug log, wait for the final
"Updating class browser...
Class browser updated."
* try again - it works now
This is a serious bug but I don't understand why the macro manager depends on CC or vice versa. Not easy to catch!
Question: does macro manager issue an error if a global var cannot be resolved or access is denied to settings or alike?!
--- End quote ---
--- End quote ---
Do you think this is the problem caused by wxExecute?
BTW: I see there are some function in CodeCompletion:
--- Code: ---Manager::Get()->GetMacrosManager()->ReplaceMacros
--- End code ---
Does this function thread safe? I can believe both CC and Compiler plugins will call it sometimes.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version