Code::Blocks Forums

Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: adam on April 03, 2007, 09:51:30 pm

Title: toolbar image not chainging state..fix??
Post by: adam on April 03, 2007, 09:51:30 pm
I was thumbing through the source yesterday seeing if i could find out maybe if it was a problem with c::b not wx and it turns out it may be. I was not able to locate at anytime the save button getting toggled/disable nor does it provide a secondary image to "grey" too which seems to be needed as per the wxtoolbar docs. If I just didn't see these too forgive me the code was kinda confusing as to finding these two things.
Title: Re: toolbar image not chainging state..fix??
Post by: Pecan on April 03, 2007, 11:25:17 pm
 Do a full project search of idFileSave.

.../src/main.cpp

Code
    if (m_pToolbar)
    {
        m_pToolbar->EnableTool(idFileSave, ed && ed->GetModified());
        m_pToolbar->EnableTool(idFilePrint, Manager::Get()->GetEditorManager() && Manager::Get()->GetEditorManager()->GetBuiltinActiveEditor());
    }

Title: Re: toolbar image not chainging state..fix??
Post by: adam on April 05, 2007, 12:48:14 am
Yes i saw that. What i mean is according to the wx manual (or at least what I understood) is that you need to define 2 images in order to have a distinct enable disable. I didn't read anything about it automatically just greying the current image.
Title: Re: toolbar image not chainging state..fix??
Post by: Baco on June 03, 2007, 06:27:15 pm
The toolbar buttons related to the debugger are changing state with no problem.
Why the toolbar save button dont change state?

Edit: I tried with nightly build 3989 in win xp
Title: Re: toolbar image not chainging state..fix??
Post by: stahta01 on June 03, 2007, 08:35:33 pm
The toolbar buttons related to the debugger are changing state with no problem.
Why the toolbar save button dont change state?


Regressions/Confirmed/Annoying/Common bugs:

  • toolbar-images-not-changing-state (is a wx problem/Win XP problem)

Note: I read on this forum that Vista does NOT have this problem.

Tim S