C / C++ / MFC

Mark Salsbery7-Jun-07 7:52

7-Jun-07 7:52

One way is to use "command enablers"...

BEGIN_MESSAGE_MAP(CMyFrameWnd, CFrameWnd)
...
ON_UPDATE_COMMAND_UI(ID_BUTTONID, OnUpdateButton)
...
END_MESSAGE_MAP()
 
void CMyFrameWnd::OnUpdateButton(CCmdUI* pCmdUI) 
{
   if (some_condition)
      pCmdUI->Enable(TRUE);
   else
      pCmdUI->Enable(FALSE);
}

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

Romiks7-Jun-07 19:41

7-Jun-07 19:41

Mark thanks for reply, but I have dialog based application, there is no ON_UPDATE_COMMAND_UI Frown | :(

Nelek8-Jun-07 3:09

Nelek

8-Jun-07 3:09

Then try in OnPaint.

if (condition)
button->EnableWindow (TRUE);
else
button->EnableWindow (FALSE);

is not the best way, but it will maybe work

NOTE: I have not read the article, so im not sure if I'm saying something catastrofical Wink | ;)

Greetings.

--------
M.D.V.

If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?

Mark Salsbery8-Jun-07 4:32

8-Jun-07 4:32

Well, anytime after a toolbar is created and the buttons are added to it, you can enable and
diable buttons when you need to:

// Disable a button
m_ToolBar.GetToolBarCtrl().EnableButton(ID_BUTTON1, FALSE);

// Enable a button
m_ToolBar.GetToolBarCtrl().EnableButton(ID_BUTTON1, TRUE);

Mark

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

Romiks8-Jun-07 18:54

8-Jun-07 18:54

Mark, many thanks it works Smile | :)

, but button was not greyed Sniff | :^)

Mark Salsbery9-Jun-07 7:51

9-Jun-07 7:51

Romiks wrote:
but button was not greyed

Looking at the article, it looks like there's a separate image list for disabled.
Are the images in that image list the same as the regular images?

You could try omitting the last parameter in the call to LoadTrueColorToolBar() - the system
should do its default "greying" for disabled buttons.

Mark

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

Romiks11-Jun-07 20:38

11-Jun-07 20:38

Mark, many thanks for help. I have tried to omit the last parameter, but it doesn't work D'Oh! | :doh:

.
I will try to use CButton instead of tool bar.

Mark Salsbery12-Jun-07 6:28

12-Jun-07 6:28

So the buttons diable but they don't look disabled?

Mark

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

Romiks16-Jun-07 23:37

16-Jun-07 23:37

Hi Mark,
If I ommited the last parameter, buttons are not disabled. Frown | :(

Mark Salsbery17-Jun-07 7:29

17-Jun-07 7:29

I just downloaded the source - I'll take a look.

Mark

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

Mark Salsbery17-Jun-07 8:09

17-Jun-07 8:09

Ok..

It all works fine in the authors demo app.

The author actually omits the last parametr in the call to CTrueColorToolBar::LoadTrueColorToolBar
for the RIGHT toolbar. So, the right toolbar shows button bitmaps grayed by the system.

For the left toolbar he uses special bitmaps for disabled buttons that don't have any color,
just white/black/grays.

All the buttons except the first three on left and right are disabled. If you try to disable them
yourself they won't look any different Smile | :)

To enable them, you can add command enablers. For example, there's 9 buttons on the toolbars.
I enabled the 7th and 8th buttons like this (in MainFrm.cpp/.h):

// In MainFrm.h
 
// add these declarations to the CMainFrame class
afx_msg void OnUpdateButton32777(CCmdUI* pCmdUI);
afx_msg void OnUpdateButton32778(CCmdUI* pCmdUI);
 
 
// In MainFrm.cpp
 
// add this to CMainFrame message map
ON_UPDATE_COMMAND_UI(ID_BUTTON32777, OnUpdateButton32777)
ON_UPDATE_COMMAND_UI(ID_BUTTON32778, OnUpdateButton32778)
 
// add these handler methods
void CMainFrame::OnUpdateButton32777(CCmdUI* pCmdUI) 
{
	pCmdUI->Enable(TRUE);
}
 
void CMainFrame::OnUpdateButton32778(CCmdUI* pCmdUI) 
{
	pCmdUI->Enable(TRUE);
}

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

Romiks17-Jun-07 18:58

17-Jun-07 18:58

Ok...
I have dialog based MFC application Wink | ;)

There is no ON_UPDATE_COMMAND_UI command Frown | :(

Mark Salsbery18-Jun-07 4:29

18-Jun-07 4:29

Romiks wrote:
I have dialog based MFC application

Oh yeah, I forgot about that, sorry Blush | :O

Well I still go back to this:

// Disable button ID_BUTTON32777 in m_ToolBar
m_ToolBar.GetToolBarCtrl().EnableButton(ID_BUTTON32777, FALSE);

// Enable button ID_BUTTON32777 in m_ToolBar
m_ToolBar.GetToolBarCtrl().EnableButton(ID_BUTTON32777, TRUE);

I'm not sure why that doesn't work for you - I just tested it in a dialog toolbar here.

Mark

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

Romiks18-Jun-07 5:52

error C2665: 'AfxBeginThread' : none of the 2 overloads can convert parameter 1 from type 'void (void)'

18-Jun-07 5:52

If you have working dialog based project, could you please send me?
my mail:losqut@yandex.ru
As for me, buttons are not greyed Frown | :(

Merge Modules

bob169727-Jun-07 7:42

bob16972

7-Jun-07 7:42

When using the Visual Studio Installer to create an installation, if I add a VC++ redistributable merge module (.msm) file to the solution, the installation puts the .dll(s) into the target directory.

Is there a way to have the installer put those in a subdirectory of the targetdir without having to open the .msi up with orca.exe and modifying stuff in there?

I'm trying to put those dll(s) in the equivalent of a bin directory along with my other dll(s) and ocx files.

shivditya7-Jun-07 7:17

shivditya

7-Jun-07 7:17

While creating simple test multithreading application ,I am getting this bug.
I made function global.I dont want to declare static,I dont know whats wrong.

void CCustom1Dlg::OnButton1()
{
// TODO: Add your control notification handler code here
int m = 5;
CWinThread* tt;
tt = AfxBeginThread(Myfunc,&m,THREAD_PRIORITY_NORMAL,0,0,NULL);
}

UINT Myfunc(LPVOID pParam)
{
int* co = reinterpret_cast<int*>(pParam);
return 0;
}
Can anyone tell me,I searched many articles for bug,and all concludes that it must be
global or static,now I have global.still bug is pidding. My project settings are proper
for run time library.

|| ART OF LIVING ||

Re: error C2665: 'AfxBeginThread' : none of the 2 overloads can convert parameter 1 from type 'void (void)'

Mark Salsbery7-Jun-07 7:27

Re: error C2665: 'AfxBeginThread' : none of the 2 overloads can convert parameter 1 from type 'void (void)'

7-Jun-07 7:27

Do you still get the error if you declare your thread proc before the call to AfxBeginThread()?

UINT Myfunc(LPVOID pParam);

void CCustom1Dlg::OnButton1()
{
// TODO: Add your control notification handler code here
int m = 5;
CWinThread* tt;
tt = AfxBeginThread(Myfunc,&m,THREAD_PRIORITY_NORMAL,0,0,NULL);
}

UINT Myfunc(LPVOID pParam)
{
int* co = reinterpret_cast(pParam);
return 0;
}

*edit* You don't want to pass &m to your thread...m can/will go out of scope before MyFunc() uses<br />
it.

Mark

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

bolivar1237-Jun-07 7:28

bolivar123

7-Jun-07 7:28

Looks like we posted a response at the same Smile | :)

time

Re: error C2665: 'AfxBeginThread' : none of the 2 overloads can convert parameter 1 from type 'void (void)'

Mark Salsbery7-Jun-07 7:29

Re: error C2665: 'AfxBeginThread' : none of the 2 overloads can convert parameter 1 from type 'void (void)'

7-Jun-07 7:29

"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder

shivditya9-Jun-07 5:34

shivditya

9-Jun-07 5:34

Sorry,delayed responce,
If I made variable global ,written function declaration,where you shown but error is very same. No Change.

|| ART OF LIVING ||

Re: error C2665: 'AfxBeginThread' : none of the 2 overloads can convert parameter 1 from type 'void (void)'

Mark Salsbery9-Jun-07 7:56