Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

UpdateUI Events Not Exactly the problem

<< < (2/3) > >>

devilsclaw:
ok thanks.. and tested out seems to work fine..

hehe well at least i had fun while it lasted.

Biplab:

--- Quote from: devilsclaw on March 29, 2007, 09:23:08 am ---ok thanks.. and tested out seems to work fine..

--- End quote ---

Does it solve the CPU spike problem which you were getting pointing to that line? IMO, it should get fixed.

devilsclaw:
yes it did.. not sure why but it did.

only problem now is that the Build Options when you click it take up 100% of one of my cpu's the screen shows up a about 1 - 2 minutes after and after that
since the events are still wrapping like crazy i have to force kill the program.. i traced it into the compileroptionsdlg.cpp

also there is a configure that is used that takes a single argument but i cant find the code where its actually defined.. i can see one that takes two and one that takes none but not one.

and the ones that take none are in different parts of the project.

Biplab:

--- Quote from: devilsclaw on March 29, 2007, 10:19:31 am ---yes it did.. not sure why but it did.

--- End quote ---

Thanks for the update. :)

IMO, it was due to the typo. Earlier C::B was trying to update menu id idMenuProjectCompilerOptions and it was pointing to a non-existent menu id (As it was not created during menu creation). Thus that line was virtually making wx to look for all possible menu ids pushing the CPU usage up. But I'm not very sure.


--- Quote from: devilsclaw on March 29, 2007, 10:19:31 am ---only problem now is that the Build Options when you click it take up 100% of one of my cpu's the screen shows up a about 1 - 2 minutes after and after that
since the events are still wrapping like crazy i have to force kill the program.. i traced it into the compileroptionsdlg.cpp

--- End quote ---

This problem needs further investigation.


--- Quote from: devilsclaw on March 29, 2007, 10:19:31 am ---also there is a configure that is used that takes a single argument but i cant find the code where its actually defined.. i can see one that takes two and one that takes none but not one.

and the ones that take none are in different parts of the project.

--- End quote ---

There are couple of configure()s. ;) The configure() that exists in compilergcc can take one or two arguments.

Download the SDK manual if you want to know more on them.

--- Quote ---http://prdownload.berlios.de/codeblocks/codeblocks_sdk_doc_r3605.chm
--- End quote ---

Regards,

Biplab

devilsclaw:
sofar it has to do with a couple things in the compileroptionsdlg.cpp

first off it does not like this at all this is one of the items causing big problems


--- Code: ---        // remove "Compiler" buttons
        wxWindow* win = XRCCTRL(*this, "btnAddCompiler", wxButton);
        wxSizer* sizer2 = win->GetContainingSizer();
        sizer2->Clear(true);
        sizer2->RecalcSizes();
        sizer2->Layout();

--- End code ---

next one it really does not like either is

--- Code: ---        DoFillTree();

--- End code ---

for some reason it likes DoFillOthers();

im still testing the code but i think all the other DoFills are causing the same kind of problem.

Navigation

[0] Message Index

[#] Next page

[*] Previous page