C / C++ / MFC

SetWindowText Problem in Release Version

8-Nov-05 4:03

WM_LBUTTONDOWN is sent for sure, maybe WM_NCHITTEST ca nbe intercepted (check for OnNcHitTest whose return value is HTCAPTION when the title bar was clicked). To be sure, try with Spy++,

~RaGE();

LittleYellowBird8-Nov-05 3:38

8-Nov-05 3:38

I am creating an edit control like this .....

editPointSize.Create(ES_CENTER|WS_VISIBLE|WS_CHILD,rectOffScreen, this, ID_EDIT_POINT_SIZE);

Then I am setting up the text in it like this .....

CString strData;<br />
strData.Format("%d", nPointSize);<br />
editPointSize.SetWindowText(strData);

If I run this under the debugger its OK, but if I compile and run a release version it crashes, any ideas?

Many Thanks,

Ali

toxcct8-Nov-05 3:57

toxcct

8-Nov-05 3:57

Alison Pentland wrote:
if I compile and run a release version it crashes

what is the error message when the application crashes please ???

TOXCCT >>> GEII power
[toxcct][VisualCalc]

-- modified at 9:57 Tuesday 8th November, 2005

LittleYellowBird8-Nov-05 4:29

8-Nov-05 4:29

Thanks for the interest, the error is,

First-chance exception in PEA Plus.exe: 0xC0000005: Access Violation.

Cheers,

Ali

Rage8-Nov-05 3:57

8-Nov-05 3:57

Alison Pentland wrote:
editPointSize.Create(ES_CENTER|WS_VISIBLE|WS_CHILD,rectOffScreen, this, ID_EDIT_POINT_SIZE);

Does this always succeed ? Try and messagebox its result.

~RaGE();

David Crow8-Nov-05 4:49

David Crow

8-Nov-05 4:49

Alison Pentland wrote:
I am creating an edit control like this .....

editPointSize.Create(ES_CENTER|WS_VISIBLE|WS_CHILD,rectOffScreen, this, ID_EDIT_POINT_SIZE);

Why are you creating the control at runtime rather than design time?

"Take only what you need and leave the land as you found it." - Native American Proverb

LittleYellowBird8-Nov-05 4:46

8-Nov-05 4:46

Reply to Rage (CP very very slow & I can't seem to reply to the correct message!)

Great idea, here's the code I tried...

	if(editPointSize.Create(ES_CENTER|WS_VISIBLE|WS_CHILD,	rectOffScreen, this, ID_EDIT_POINT_SIZE))<br />
	AfxMessageBox("Edit OK");<br />
else<br />
	AfxMessageBox("FAIL FAIL FAIL!!!");

It always returned TRUE, 'Edit OK' and still crashed when I did SetWindowText.

Smile | :)

Thanks for the help, I'm not sure what to do next, so if you have any more ideas they will be gratefully received.

Cheers,

Ali

-- modified at 11:37 Tuesday 8th November, 2005

LittleYellowBird8-Nov-05 5:18

8-Nov-05 5:18

Erm, good question.

I am using MFC VC++ 6, and creating the edit box in the view window. I always create controls in dialog boxes at design time but I always create them in the view window at runtime. I have always done it that way, not sure if its right but it normally works. To be honest I don't know how else to do it, the designer thingy is only for dialog boxes isn't it?

Thanks for the input, any suggestions gratefully received Smile | :)

Ali

Rage8-Nov-05 5:54

8-Nov-05 5:54

Alison Pentland wrote:
SetWindowText

Since it is release, how do you know that it crashes when you do SetWindowText ? I suppose it works when you comment it out ?

So, if the creation of the edit control works, it is assigned a handle, and SetWindowText should not crash. Let's see what we have:

1. SetWindowText is not called before the edit box creation, since you see your messagebox before the failure.

2. The code works in debug -> have you used a #if __DEBUG somewhere, or made an ASSERT(md.InitMyVariable()) that would drop any intialisation in Release mode ?

3. Are you sure that SetWindowText fails ?

4. Have you created your edit control editPointSize locally (on the stack) in function A, and called SetWindowText in function B, so that the edit control gets erased at the end of A and does not exist anymore at B point ?

5. Temporarily enable debugging in release build using the project options, maybe it can help.

6. Check on CP for the article named "Surviving the Release" or something like this (sorry no time for a link, I got to leave in a couple of minutes), there may be good hints in there.

Good luck,

~RaGE();

David Crow8-Nov-05 6:08

David Crow

8-Nov-05 6:08

Why not just use a CFormView? With it, you can have a view with controls that are normally placed on dialogs.

"Take only what you need and leave the land as you found it." - Native American Proverb

LittleYellowBird8-Nov-05 21:44

8-Nov-05 21:44

Hi Rage,

Thanks for your reply.

Rage wrote:
1. SetWindowText is not called before the edit box creation, since you see your messagebox before the failure.

Definetly not, I have checked this because I thought that maybe the cause too.

Rage wrote:
2. The code works in debug -> have you used a #if __DEBUG somewhere, or made an ASSERT(md.InitMyVariable()) that would drop any intialisation in Release mode ?

No, I am fairly sure that I haven't used anything like that, I don't recall ever using them and no one else has worked on this code.

Rage wrote:
3. Are you sure that SetWindowText fails ?

I use that line twice, once at initialisation and later to update the edit control. I used a messge box to determine where it failed and it was at the SetWindowText in the initialisation. If I remove that line it gets through the initialisation and runs ok until I try to update the edit control, then it fails. So I am pretty sure SetWindowText is the closely related to the problem.

Rage wrote:
4. Have you created your edit control editPointSize locally (on the stack) in function A, and called SetWindowText in function B, so that the edit control gets erased at the end of A and does not exist anymore at B point ?

No, the edit control is a member of the class and therefore it should be fine (however, I have declared it in a seperate include file to try to keep my class tidy, it should not be a problem but I will check it out)

Rage wrote:
5. Temporarily enable debugging in release build using the project options, maybe it can help.

I've never done this, I will give it a try.

Rage wrote:
6. Check on CP for the article named "Surviving the Release" or something like this (sorry no time for a link, I got to leave in a couple of minutes), there may be good hints in there.

Good idea, now you mention it I've seen an article like that, I will find it up.

Also, your suggestions have made me wonder a bit more about the problem. I have lots of controls created like this, but commented them out to concentrate on one problem at a time. I think I will try to discover if the problem is with all edit controls or just some (or just one) of them.

Thanks for your help, CP was very slow for me yesterday and I also have to leave but you have been really helpfull,

Rage wrote:
Good luck,

Thanks,

Ali

LittleYellowBird8-Nov-05 22:13

8-Nov-05 22:13

Hi David,

Thanks for the idea, I most probably could do that, but I don't understand why I am having a problem with SetWindowText the way I am doing it.

Even if I did change my whole method I think I would like to get to the bottom of this problem because I need to know if I am doing something silly or if I have a fundamental misunderstanding of what I am doing, because I think what I am doing should work.

Anyway, thanks for the advice - I will keep it in mind Smile | :)

Ali

Rage15-Nov-05 21:18

15-Nov-05 21:18

Hi Alison,

got this eventually sorted out ?

~RaGE();

LittleYellowBird30-Nov-05 5:14

cannot open file(image) that saved

30-Nov-05 5:14

Hi ~RaGE();

Sorry its taken me so long to reply, I haven't been around for a while.

Yes I have sorted it out and it turned out to be my own silly error Blush | :O

It turned out not to be in SetWindowText but in a function called "OnEditPointSize". It was called when I set the text size.

Instead of declaring it like this:-

void CPPlusView::OnEditPointSize(void)

I had declared it like this WTF | :WTF:

:-

void CPlusView::OnEditColourBands(NMHDR* pNMHDR, LRESULT* pResult)

Its my own fault, I've used cut & paste when I first created the function and forgotten to change the parameters. It actually crashed when it left the function, I guess it messed up the stack.

I found it by starting the simplest program I could, then I recreated the problem by adding code in from my application. Then I had so little code to look through I soon found it.

Thanks for the help, you gave me some new ideas to try which was definetly a big help. Sometimes I get stuck with a bug and I just can't think how to find it!

Thanks Again Big Grin | :-D

Ali

sue8-Nov-05 3:01

sue

8-Nov-05 3:01

hi there..have used twain program,but when i tried to open the file back, it not available.anyone have idea about this? firstly when save it automatically save in any files. then i tried to save with putting .bmp or .jpg but it still cannot open. maybe something wrong in DIB coding.someone please explain me why its happen and how to solve it.thanks.
please someone help me, urgent! Frown | :(

- sue -

Splitted MDI Client (MFC)

Andre xxxxxxx8-Nov-05 2:12

Andre xxxxxxx

8-Nov-05 2:12

I am developing an MDI application where each document can have up to 60 views. To manage the views and documents i've subclassed the MDI client and added tabs on the top to switch between the documents/files.

But i want to be able to compare the documents/files side by side. Therefore i would like to create a splitter window inside the MDI client (http://www.codeproject.com/splitter/kaldysimplesplitter.asp[^]) and display the child windows (CMDIChildWnd) for each document inside a pane.

But unfortunately the MFC makes the assumption that the MDI frame is two parents up of the child window and if the MDI client is not the parent MFC crashes.

Any suggestions?

Thanks
Andre

Repainting mechanism in VC++ ...OnPaint()

maharaja pandian8-Nov-05 1:49

maharaja pandian

8-Nov-05 1:49

hi,
i am displaying a rectangular box in the window on OnLButtonDown event
using

CClientDC dc(this);
dc.Rectangle(5,5,100,50);

when i minimizing or maximizing the window the rectangular box would vanished(not visible) .,because of OnPaint event
so i try with CDC class to convert all image window Bitmap and store it in
the memory .on OnPaint event i once again call the CDC to show the window image
using

void CChildView::OnLButtonDown(UINT nFlags,CPoint point)
{
CDC MemDC;
CClientDC dc(this);
MemDC.CreateCompatibleDC(&dc);
CBitmap *pOldBitmap = MemDC.SelectObject(&m_Bitmap);
MemDC.SetBkMode(TRANSPARENT);
dc.SetBkMode(TRANSPARENT);
MemDC.Rectangle(5,5,100,50);
dc.Rectangle(5,5,100,50);
}
void CChildView::OnPaint()
{

CDC MemDC;
CPaintDC PaintDC(this);
MemDC.CreateCompatibleDC(&PaintDC);
MemDC.SelectObject(&m_Bitmap);
PaintDC.BitBlt(PaintDC.m_ps.rcPaint.left,PaintDC.m_ps.rcPaint.top,
PaintDC.m_ps.rcPaint.right - PaintDC.m_ps.rcPaint.left,
PaintDC.m_ps.rcPaint.bottom - PaintDC.m_ps.rcPaint.top,
&MemDC,PaintDC.m_ps.rcPaint.left,PaintDC.m_ps.rcPaint.top,
SRCCOPY);
}

Even after using this code , i didn't get the original rectangular box
when i maximizing the window.
reply as soon as possible
Smile | :)

send reply

Re: Repainting mechanism in VC++ ...OnPaint()

Calc208-Nov-05 2:17

Calc20

8-Nov-05 2:17

In OnLButtonDown try to deselect m_Bitmap from MemDC by calling MemDC.SelectObject(pOldBitmap).
Also you could declate MemDC as a class member that way in OnPaint you just have to call Bitblt.

Re: Repainting mechanism in VC++ ...OnPaint()

Nibu babu thomas8-Nov-05 17:09

Nibu babu thomas

8-Nov-05 17:09

Inside 'OnPaint' try using 'CClientDC' instead of 'CPaintDC'

Nibu thomas.
Software Developer.

Repainting mechanism in VC++ ...OnPaint()

maharaja pandian8-Nov-05 1:47

maharaja pandian

8-Nov-05 1:47

hi,
i am displaying a rectangular box in the window on OnLButtonDown event
using
CClientDC dc(this);
dc.Rectangle(5,5,100,50);
when i minimizing or maximizing the window the rectangular box would vanished
because of OnPaint event
so i try with CDC class to convert all image window Bitmap and store it in
the memory .on OnPaint event i once again call the CDC to show the window image
using

void CChildView::OnLButtonDown(UINT nFlags,CPoint point)
{
CDC MemDC;
CClientDC dc(this);
MemDC.CreateCompatibleDC(&dc);
CBitmap *pOldBitmap = MemDC.SelectObject(&m_Bitmap);
MemDC.SetBkMode(TRANSPARENT);
dc.SetBkMode(TRANSPARENT);
MemDC.Rectangle(5,5,100,50);
dc.Rectangle(5,5,100,50);
}
void CChildView::OnPaint()
{

CDC MemDC;
CPaintDC PaintDC(this);
MemDC.CreateCompatibleDC(&PaintDC);
MemDC.SelectObject(&m_Bitmap);
PaintDC.BitBlt(PaintDC.m_ps.rcPaint.left,PaintDC.m_ps.rcPaint.top,
PaintDC.m_ps.rcPaint.right - PaintDC.m_ps.rcPaint.left,
PaintDC.m_ps.rcPaint.bottom - PaintDC.m_ps.rcPaint.top,
&MemDC,PaintDC.m_ps.rcPaint.left,PaintDC.m_ps.rcPaint.top,
SRCCOPY);
}

Even after using this code , i didn't get the original rectangular box
when i maximizing the window.
Smile | :)

send reply

Tree ctrl label edit

LiYS7-Nov-05 22:31

LiYS

7-Nov-05 22:31

In what conditions tree items can not be edited through clicking the label of that item?

I didn't intercept any mouse click message, and the ctrl also has the TVS_EDITLABELS style, but when I click the item label the break point in OnBeginlabeledit(...) doesn't reached.

Re: Tree ctrl label edit

*Dreamz7-Nov-05 23:36

*Dreamz

7-Nov-05 23:36

You can edit the label by clicking the item which is currently in the selected state.

I think OnBeginlabeledit wont be fired when you move the focus to a new item by clicking it. Try clicking it again, i think then it will fire the event.

Re: Tree ctrl label edit

LiYS8-Nov-05 2:28

LiYS

8-Nov-05 2:28

*Dreamz wrote:
You can edit the label by clicking the item which is currently in the selected state.

Exact the scenario which I talk about in the original message

*Dreamz wrote:
I think OnBeginlabeledit wont be fired when you move the focus to a new item by clicking it. Try clicking it again, i think then it will fire the event.

I click the item label several times constantly, OnBeginlabeledit just doesn't get fired D'Oh! | :doh:

Re: Tree ctrl label edit

Rage8-Nov-05 4:08