C / C++ / MFC

21-Mar-09 13:36

for (int l=0;l<5;l++)
{
	DBGetText(hWndGet);
	TextInfoSend(hWndSend, ts);
	hTimer = CreateWaitableTimer(NULL, FALSE, NULL);
	LARGE_INTEGER liDueTime;
	liDueTime.QuadPart = -1000LL;
	SetWaitableTimer(hTimer, &liDueTime, 0, NULL, NULL, 0);
	(WaitForSingleObject(hTimer, INFINITE) != WAIT_OBJECT_0);
	CancelWaitableTimer(hTimer);
All the above minus the for loop works when inserted in a command button.

/////The following helps to comeout of the loop whenever notepad is closed
	HWND hWnd1;
	hWndout = FindWindow("NotePad",NULL);
	if (hWndout)
	{
		l=2;
	}
////////////////////////////////////////////////////////////////////////
}

After having done the for loop my data only refreshes when I exit the loop.

BTW I am using WM_COPYDATA inside TextInfoSend function to transmit data.

Can someone shed somelight as to what I have missed to get my data to refresh.

Thanks A Million.

Code-o-mat21-Mar-09 23:42

21-Mar-09 23:42

I'm not completely sure what you are trying to accomplish there but my guess would be that your loop runs in your GUI thread, this means, no messages will be processed during the workings of the loop, thus the unrefreshed and unreponsive GUI (if your loop takes longer then windows will also consider your process unreponsive and you probably will get the nice "Not responding..." text in the titlebar of your main window - if you have one that is). To avoid this you can try putting your loop in a separate thread.

> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> Life: great graphics, but the gameplay sux. <

FISH78622-Mar-09 0:23

22-Mar-09 0:23

Yes. That is whats happening. I guess since i am new at this, there was nothing in the code that I have done wrong. My next dumb question is How do I create a new process from the GUI.

thanks a million.

Code-o-mat22-Mar-09 0:50

22-Mar-09 0:50

I asusme you meant "tread", not "proccess", i recommend reading this[^] for starters and then checking out CreateThread[^]. After that, if you have questions, feel free to ask.

> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> Life: great graphics, but the gameplay sux. <

FISH78622-Mar-09 1:45

22-Mar-09 1:45

Thank you. I found a prototype to use one too. That does work perfectly for about 10 minutes or so.

After the 10 minutes I get an error which says my buffer is too small.

Withinn other functions of the application, I know I am clearing all variables and closing and reopening the file in one function and as soon as the writing is done I am closing the file and clearing the variables.

Any suggetions as to where I could be going wrong?.

Code-o-mat22-Mar-09 7:33

22-Mar-09 7:33

Well, without seeing your code it's hard to say...try finding out if your 'cleanup code' really gets called or not by placing breakpoints, or TRACE-es, or a message box, or or or...

> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> Life: great graphics, but the gameplay sux. <

FISH78622-Mar-09 7:55

22-Mar-09 7:55

Here is the section I am having problems with:

This is in a function of it's own:

Instead of using WindowFromPoint I am using hWnd that I have for the window
I am after since the user could have moved it.
POINT Textpt;
Textpt.x = a;
Textpt.y = c;
HDC DlgDC,MemDC,DeskDC;
int height, width;
HBRUSH hBrush;
HBITMAP hBitmap;
DlgDC = GetDC(hWnd);
DeskDC = GetDC(NULL);
hBrush = CreateSolidBrush(RGB(255,25,0));
width= 53;
height= 8;
MemDC = CreateCompatibleDC(DlgDC);
hBitmap = CreateCompatibleBitmap(DlgDC,width,height);
SelectObject(MemDC,hBitmap);
BitBlt(MemDC,0,0,width,height ,DeskDC,Textpt.x,Textpt.y,SRCCOPY);
////
Some processing....
Couple of If statements and geting color pixels.
////
after above is done processing->

ReleaseDC(NULL,MemDC);
DeleteObject(MemDC);
ReleaseDC(NULL,DlgDC);
DeleteObject(DlgDC);
ReleaseDC(NULL,DeskDC);
DeleteObject(DeskDC);

Please help if its wrong...
This is the only part that dies after 10 minutes. I ran this with the thread, I commented the rest of the app including the processing in between the above code.
I ran the thread own its own without the above it ran fine. All the thread was doing at that point was getting the handle to the window I am after.It ran for a long time.
Thanks a million.

Code-o-mat22-Mar-09 8:19

22-Mar-09 8:19

This:
MemDC = CreateCompatibleDC(DlgDC);
must be "freed" like this:
DeleteDC(MemDC);
ReleaseDC does not need to be used for the memory DC, and DeleteObject is not for device contexts at all.

This:
DlgDC = GetDC(hWnd);
needs to be released like this:
ReleaseDC(hWnd, DlgDC);
ReleaseDC(NULL, DlgDC) is wrong, you need to specify the same window handle you used to get the DC. And once again, don't use DeleteObject for a DC.

Also note, when you select objects into a DC, may those be bitmaps or brushes or whatever, the original objects should be select back into the DC before you delete the DC or delete objects that were selected into the DC. To explain this a bit more clearly:
This is not complete:

HDC MemDC = CreateCompatibleDC(DlgDC);
HBITMAP bitmap = CreateCompatibleBitmap(MemDC, 100, 100);
SelectObject(MemDC, bitmap);
...
DeleteDC(MemDC);
DeleteObject(bitmap);

Should be done something like this:

HDC MemDC = CreateCompatibleDC(DlgDC);
HBITMAP bitmap = CreateCompatibleBitmap(MemDC, 100, 100);
HBITMAP originalbitmap = (HBITMAP)SelectObject(MemDC, bitmap);
...
SelectObject(MemDC, originalbitmap);
DeleteDC(MemDC);
DeleteObject(bitmap);

If you do not follow this "rule", your program will leak GDI resources...

Also one very important thing you should know about threads is that fiddling with GUI objects in other than the GUI thread is strongly not recommended.

> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> Life: great graphics, but the gameplay sux. <

FISH78622-Mar-09 8:30

22-Mar-09 8:30

thanks a million. I will change a few things and give it a try.

FISH78622-Mar-09 10:28

how to use in-place editing

22-Mar-09 10:28

Same thing in about 15 to 20 minutes at least it took a bit longer. I have a question. I am trying to capture text from an external app. the text on the app is being populated with WM_PAINT. Not sure even if a WM_PAINT hook to this application will help. What are my choices if this keeps not responding to the route I have taken.?

jiaweicz21-Mar-09 11:01

jiaweicz

21-Mar-09 11:01

Oh,I'm sorry, my english is poor, how to use the in-place editing of microsoft?

example: Microsoft Word and Microsoft Equation Eidtor(in the word), what do it? ,in the program use word
thank you

Re: how to use in-place editing

Yusuf21-Mar-09 13:02

Yusuf

21-Mar-09 13:02

what are you talking about. You are in the wrong forum.

Yusuf

Oh didn't you notice, analogous to square roots, they recently introduced rectangular, circular, and diamond roots to determine the size of the corresponding shapes when given the area. Luc Pattyn[^]

XP/Vista Styles

The_Judgement21-Mar-09 9:27

21-Mar-09 9:27

Hi, I have a problem when I want to use de XP/Vista Styles for Common Controls. As I'm using Visual Studio 2008, at the beggining of the code I put:

#pragma comment(linker,"/manifestdependency:\"type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='*' publicKeyToken='6595b64144ccf1df' language='*'\"")

I read in the MSDN it is not neccesary add a manifest if I include that (if I use a manifest in XP the controls disappeard but the program works), but when I execute the program in XP, i get a error message, something like "Reinstallation of the program could solve the issue", on the other hand, in Vista works fine and the controls have the Vista style. ¿What is wrong?

Thanks

Code-o-mat21-Mar-09 10:35

21-Mar-09 10:35

Did you call InitCommonControlsEx[^]? Aside of that, i believe "Reinstallation of the program could solce the issue" you usually get when your program uses a DLL the system cannot find...

> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> Life: great graphics, but the gameplay sux. <

The_Judgement21-Mar-09 11:14

21-Mar-09 11:14

No, I didn't use that function, but I think it is not necessary because in most pages where I look: http://www.zhornsoftware.co.uk/a_xp/index.html[^] or: http://weseetips.com/2008/12/30/how-to-enable-xpvista-themes-in-your-dialog/[^] don't explain anything about the use of that function.

About if dll does not exist, I've execute the program in other XP and it works, but when I open the Dialog Box where the controls are, simply does not appears, but the program execute fine. It's the same problem when I use the manifest and I don't know why it occurs.

Anyway, thanks for your reply.

Code-o-mat21-Mar-09 11:27

21-Mar-09 11:27

After trying to create the dialog use GetLastError to find out why it did not get created. I have seen behaviour like that in at least 3 cases:
-the resource of the dialog did not exist, since you say it works fine under Vista i'd say that is not the case
-the dialog had some control on it which could not be created because its class was not registered, like custom controls we forgot to explicitly register before trying to brign up the dialog.
-usage of an ActiveX control on the dialog which was not registered on the system.

There might be tonns of other reasons of course...could it be that you are using some "special" control (ActiveX?) on your dialog that needs explicit registering under XP but it is registered already/by default under Vista?

> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> Life: great graphics, but the gameplay sux. <

The_Judgement21-Mar-09 12:41

21-Mar-09 12:41

I've call GetLastError after create the dialog box, but it returns 0, and DialogBox returns -1. Looking at MSDN I saw 4 possible errors, althought none of them I think are the problem:

-an invalid parameter value
-the system class was registered by a different module
-The WH_CBT hook is installed and returns a failure code
-if one of the controls in the dialog template is not registered, or its window window procedure fails WM_CREATE or WM_NCCREATE

I don't understand why does not work, because the controls inside the dialog box are edit and buttons controls, only that. I put the code of the definition of the dialog box:

NewDialogBox DIALOGEX 170,70,250,150<br />
STYLE DS_MODALFRAME | WS_POPUP | WS_CAPTION | WS_SYSMENU<br />
CAPTION "Nuevo"<br />
FONT 10, "Tahoma"<br />
BEGIN<br />
	DEFPUSHBUTTON "Aceptar", IDOK | WS_TABSTOP, 95, 130, 50, 14<br />
	PUSHBUTTON "Cancelar", IDCANCEL | WS_TABSTOP, 165, 130, 50, 14<br />
	CONTROL "Anchura", IDS_WEIGHT, "static", <br />
    SS_LEFT | WS_CHILD | WS_VISIBLE, <br />
    20, 50, 150, 8<br />
	CONTROL "", IDE_WEIGHT, "edit", <br />
    SS_LEFT | WS_CHILD | WS_VISIBLE | WS_BORDER | WS_TABSTOP, <br />
    100, 50, 100, 12<br />
	CONTROL "Altura", IDS_HEIGHT, "static", <br />
    SS_LEFT | WS_CHILD | WS_VISIBLE, <br />
    20, 70, 150, 8<br />
	CONTROL "", IDE_HEIGHT, "edit", <br />
    SS_LEFT | WS_CHILD | WS_VISIBLE | WS_BORDER | WS_TABSTOP, <br />
    100, 70, 100, 12<br />
END

Thanks.

Code-o-mat21-Mar-09 23:04

Re: XP/Vista Styles [modified]

21-Mar-09 23:04

Hmm...did you try stepping thorough the code (during runtime i mean by setting a breakpoint and using "Step into" and such tools) to see where it fails? Does the dialog show if you remove the controls from it? If yes, maybe try putting them back one by one and see when the dialog stops showing...

> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> Life: great graphics, but the gameplay sux. <

The_Judgement22-Mar-09 11:28