C / C++ / MFC

floating CDialogBar remains on screen when clicking the close button

4-Apr-06 7:24

Manu_81 wrote:
I also want to run a batch file...

See here.

"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain

"There is no death, only a change of worlds." - Native American Proverb

freddylowski4-Apr-06 6:37

freddylowski

4-Apr-06 6:37

Hi there,

I'm using some CDialogBars in my Application. If they are floating and I click the close-button the controls on the bar disappear. But the window containing the bar remains on screen.
It disappears only when dragging the empty window on a position where it could dock.

Using exactly the same dialogbar in an example application worked fine.

Does anyone have an idea why it behaves like this?

How do I keep menu attributes that exist when the menu refreshes?

jonesap54-Apr-06 6:10

jonesap5

4-Apr-06 6:10

I am trying to disable some menu items in a menu. I am successful in getting the menu items disabled using the function SetMenuItemInfo; but when the menu refreshes the items are re-enabled and I don't want that. Is there anything that I can do to disable menu items from refresh or recreate of the menu?

thanks,

Re: How do I keep menu attributes that exist when the menu refreshes?

David Crow4-Apr-06 7:27

Re: How do I keep menu attributes that exist when the menu refreshes?

4-Apr-06 7:27

jonesap5 wrote:
...but when the menu refreshes the items are re-enabled...

During the refresh, are you calling SetMenuItemInfo() or EnableMenuItem()?

"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain

"There is no death, only a change of worlds." - Native American Proverb

jonesap54-Apr-06 7:30

jonesap5

4-Apr-06 7:30

What happens is I select submenu item from the 'Tool' Menu and it refreshes or recreates the main menu. At that point the sub menu items I disabled in the 'File' Menu are re-enabled. Does that make sense?

Re: How do I keep menu attributes that exist when the menu refreshes?

Michael Dunn4-Apr-06 11:31

Michael Dunn

4-Apr-06 11:31

If you're using MFC, read this FAQ:
7.1 In my MFC program, I'm trying to disable a menu item with EnableMenuItem(), but it doesn't have any effect on the menu. Why?[^]

--Mike--
Visual C++ MVP Cool | :cool:

LINKS~! Ericahist | NEW!! PimpFish | CP SearchBar v3.0 | C++ Forum FAQ

Re: How do I keep menu attributes that exist when the menu refreshes?

jonesap54-Apr-06 12:21

jonesap5

4-Apr-06 12:21

I am not using MFC, I am actually using a Win32 project.

kill COM calls in thread

viperlogic4-Apr-06 5:47

4-Apr-06 5:47

i have a thread that calls the following

CoInitializeEx()
CoInitializeSecurity()
CoCreateInstance()
ConnectServer()

if the thread isnt successful in 3secs (using WaitForSingleObject(pThread->m_hThread, 3000)) it is closed.

what is the best way of killing a thread from outside the thread, i am using TerminateThread() but i dont think this is the best way??

it appears thou that the calls in the thread are not being killed off because if i go to start the thread again CoInitializeSecurity() throws up an error saying that it cant initialize security. so iam assuming it is saying this because the thread wasnt killed off right

plz help

ThatsAlok4-Apr-06 6:46

ThatsAlok

4-Apr-06 6:46

viperlogic wrote:
what is the best way of killing a thread from outside the thread, i am using TerminateThread() but i dont think this is the best way??

Set a boolean varible depending on it state terminate the thread

viperlogic4-Apr-06 6:56

4-Apr-06 6:56

what command do i use to kill the thread thou from outside the thread?

ThatsAlok4-Apr-06 7:05

ThatsAlok

4-Apr-06 7:05

viperlogic wrote:
what command do i use to kill the thread thou from outside the thread?

same, change the value of boolean variable from outside, which thread is checking from inside...

viperlogic4-Apr-06 7:40

4-Apr-06 7:40

sorry, i dont understand, example please

thanks

David Crow4-Apr-06 7:28

4-Apr-06 7:28

viperlogic wrote:
what is the best way of killing a thread from outside the thread...

See here.

"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain

"There is no death, only a change of worlds." - Native American Proverb

viperlogic4-Apr-06 8:01

4-Apr-06 8:01

so i use the following to delete a thread from outside?? Does "delete pThread" call ExitThread??

switch(WaitForSingleObject(pThread->m_hThread, 3000))
{
case WAIT_TIMEOUT:
{
delete pThread;
break;
}

case WAIT_OBJECT_0:
{
// thread has terminated on its own
break;
}
}

David Crow4-Apr-06 8:13

4-Apr-06 8:13

viperlogic wrote:
Does "delete pThread" call ExitThread??

No. At the point in which you are deleting pThread, the thread has already terminated. You are just cleaning up the CWinThread object.

ExitThread() is called from within the secondary thread, unlike TerminateThread() which is called from outside the secondary thread.

"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain

"There is no death, only a change of worlds." - Native American Proverb

viperlogic4-Apr-06 10:19

4-Apr-06 10:19

i think i have that working now.

A kind of related problem i have is with the code below. This is a part of the code the thread executes, if sucessful all is ok. this thread has a timeout of 3secs. A problem is that the ConnectServer call below takes 2minutes to complete if it cant connect. when this happens the below messagebox pops ups and then the program crashes. is it crashing because the code wants to "return" but there is nothing to return to as the thread has been already killed?? How can i modify it so that it wont crash. A message box doesnt have to be displayed either.

many thanks

<br />
	hres = pLoc_test->ConnectServer(<br />
		_bstr_t(L"\\\\"+strIP1+"\\root\\cimv2"),		// Object path of WMI namespace<br />
        NULL,												// User name. NULL = current user<br />
        NULL,												// User password. NULL = current<br />
        0,													// Locale. NULL indicates current<br />
        WBEM_FLAG_CONNECT_USE_MAX_WAIT,						// Security flags<br />
        0,													// Authority        <br />
        0,													// Context object <br />
        &pSvc_test												// pointer to IWbemServices proxy<br />
        );<br />
<br />
    <br />
    if (FAILED(hres))<br />
    {<br />
       	char error_msg[64];<br />
		sprintf(error_msg, "wmi_test: Could not connect. Error code = 0x%x", hres);<br />
		MessageBox(error_msg , "Error" , MB_ICONERROR | MB_OK);<br />
<br />
        pLoc_test->Release();     <br />
        return;    	<br />
    }<br />

David Crow4-Apr-06 10:37

4-Apr-06 10:37

Since you are using WBEM_FLAG_CONNECT_USE_MAX_WAIT, why not set your WaitForSingleObject() call to also wait for 2 minutes (or a little more)?

"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain

"There is no death, only a change of worlds." - Native American Proverb

viperlogic4-Apr-06 10:41