Comments by Kucera Jan

Kucera Jan 19-Mar-14 4:12am View

I WOULD REALY LIKE TO KNOW WHO IS THE ONE THA MARKED THIS AS "ACCEPTED SOLLUTION" !!!
Despite that I appreciate your willingness to help and answer, this answer DOES NOT SOLVE the problem itself at all. Such answer acceptations shall be forbidden. This is good just for collecting points, but it does not serve the purpose of the forum at all !!!

Kucera Jan 19-Mar-14 4:09am View

Sure, sure. You can compute and use an offset only for an array (or sub-array) that is in a continuous part of memory - that is obvious.

Kucera Jan 17-Mar-14 13:30pm View

It is a new TFS workspace, and the sources are "latest version". Does not help :(

Kucera Jan 17-Mar-14 13:28pm View

Thanks, much. But I have the set-up correct I believe. This is not my first time I am debugging remotely. The problem is that I created a new workspace and since then (probably) I cannot do the debugging. The trouble is that they dymbol file is correctly loaded (according to the module view in VS2010) but probably not used - as if it was corrupted. Finally I found that I cannot remote-debug from the old workspaces either...

Kucera Jan 17-Mar-14 13:06pm View

Hi, thanks for reply. I do have the source code and generation of Debug Info is enabled in both Release and Debug configuration. But still no success. It seems as if the pdb file (that I got during the DLL compilation) was somehow corrupted or so... Any other idea ? Thx

Kucera Jan 29-May-13 3:07am View

Actually it would be more appropriate to test it for a non-zeor value, like this:

BOOL isVisible = ((myWindowStyle & WS_VISIBLE) != 0);

Kucera Jan 27-May-13 5:29am View

Many thanx for your advice. A lot of things are obvious, though sometimes cannot be seen. If you insinst on such point of you, do not bother to attend any forums.
J.K.

Kucera Jan 23-May-13 8:57am View

Aha, I see. So you just call the GetDlgItem(nID) not on pointer |this| (which is the main window), but you shall call it on each of the dialogs - like pDialog->GetDlgItem(nId)...

Or you might find handy a pure WinAPI call that acceps an extra argument the dialog handle (HWND) ::GetDlgitem(). but I would recoment the first posiiblility.

Kucera Jan 23-May-13 4:05am View

Well, that perhaps means that the dialogbox (to whuich you have pointer in pointer this) cannot find the component. This might be cause by one of the following reason:
- the components parent is not directly the dialog but some different class, like
Dialog
|
+-ImmediateComponent
|
+- Your component // this cannot be found by the DialogBox

- You are using wrong nId of the component and so it cannot be found

- make sure that the dialog is really pointed to by |this| pointer and that it properly derives from MFC CDialog.

Kucera Jan 15-May-13 4:25am View

You are very welcome, dont hesitate to ask more if needed...

Kucera Jan 15-May-13 3:39am View

Definitelly, thanx for comment.

Kucera Jan 22-Apr-13 3:11am View

Hi,

thanx for reply. If I can ask you, restore my answer - if possible. In case you insist ojn your answer, put it as a comment or create a new answer or just append your answer to mine.

thanx in advance
J. K.

Kucera Jan 19-Apr-13 9:56am View

Dear "friend",

next time it would be pollite to ASK before you start to "reconstruct" my articles/answers.
E.g. you completely changed the meaning of "Pattern II." of my answer. Further, the code was not buggy... maybe you just have to modify it a bit before you use it, thats all.

Next time, discuss before updating OR post your own answer.

Regards,
J. K.

Comments by Kucera Jan (Top 13 by date)