C / C++ / MFC

Re: Create a button whose id is ID_FILE_NEW, not be processed by CWinApp::OnFileNew

10-Apr-08 23:39

SDI, can't CMyApp::OnFileNew handle the the click message by the button?

int CMyView::OnCreate(LPCREATESTRUCT lpCreateStruct) 
{
  ...
  m_btnNew.Create(NULL,style,rcDummy,this,ID_FILE_NEW);
  m_btnNew.LoadBitmaps(IDB_NEW,IDB_NEW_DOWN);
}

Nitheesh George11-Apr-08 2:03

Nitheesh George

11-Apr-08 2:03

Hi,
have you mapped the WM_COMMAND to CWinApp::OnFileNew.?

thanks

Nitheesh

Re: Create a button whose id is ID_FILE_NEW, not be processed by CWinApp::OnFileNew

followait11-Apr-08 3:41

Re: Create a button whose id is ID_FILE_NEW, not be processed by CWinApp::OnFileNew

11-Apr-08 3:41

No, I just created a button using ID_FILE_NEW.

Nitheesh George11-Apr-08 4:29

Nitheesh George

11-Apr-08 4:29

hi,

then u have to map the WM_COMMAND for the Button Id in following way. ON_COMMAND(ID_FILE_NEW,CWinApp::OnFileNew)

thanks

Nitheesh

Re: Create a button whose id is ID_FILE_NEW, not be processed by CWinApp::OnFileNew

followait11-Apr-08 5:22

Re: Create a button whose id is ID_FILE_NEW, not be processed by CWinApp::OnFileNew

11-Apr-08 5:22

It's there in CMyWinApp as part o fthe framework.
I don't why the message is not pumped there.

Nitheesh George11-Apr-08 6:45

Nitheesh George

11-Apr-08 6:45

Hi,

this is because the BN_CLICKED message is posted into the Parent Windows message queue. that is why the message is not getting into CWinApp.

thanks

Nitheesh.

Re: Create a button whose id is ID_FILE_NEW, not be processed by CWinApp::OnFileNew

followait11-Apr-08 7:09

Re: Create a button whose id is ID_FILE_NEW, not be processed by CWinApp::OnFileNew

11-Apr-08 7:09

But CWinApp::OnFileNew is a protected member function, so I couldn't add the following line to CMyView:

ON_COMMAND(ID_FILE_NEW,CWinApp::OnFileNew);

any quick way?

followait11-Apr-08 7:18

What is wrong with this iterator?

11-Apr-08 7:18

I found the problem,
If a view receives a message it will go through the view's and doc's msg maps, the app's msg map will not be searched.

vikramlinux10-Apr-08 22:41

vikramlinux

10-Apr-08 22:41

<br />
vector<int> myIntVector;<br />
vector<int>::iterator myIntVectorIterator;<br />
<br />
// Add some elements to myIntVector<br />
myIntVector.push_back(1);<br />
myIntVector.push_back(4);<br />
myIntVector.push_back(8);<br />
<br />
for(myIntVectorIterator = myIntVector.begin(); <br />
        myIntVectorIterator <= myIntVector.end();<br />
        ++myIntVectorIterator)<br />
{<br />
    cout<<*myIntVectorIterator<<" ";<br />
    //Should output 1 4 8<br />
}<br />

vikramlinux10-Apr-08 22:46

vikramlinux

10-Apr-08 22:46

This code crashes on windows.

while on gcc 2.95.3 on unix
I get an output like
1 4 8 0

Cedric Moonen10-Apr-08 22:58

Cedric Moonen

10-Apr-08 22:58

vikrams wrote:
while on gcc 2.95.3 on unix
I get an output like
1 4 8 0

That's wrong. The code should throw an exception because you try to access the contents of an iterator outside the bounds of your vector.

Cédric Moonen
Software developer

Charting control [v1.3]

Stephen Hewitt13-Apr-08 14:21

Stephen Hewitt

13-Apr-08 14:21

Cedric Moonen wrote:
That's wrong. The code should throw an exception because you try to access the contents of an iterator outside the bounds of your vector.

The C++ standard does not require an exception to be thrown in this case. The behaviour is undefined.

Steve

Rajesh R Subramanian10-Apr-08 23:04

Rajesh R Subramanian

10-Apr-08 23:04

vikrams wrote:
while on gcc 2.95.3 on unix
I get an output like
1 4 8 0

I think your gcc 2.95.3 sucks and you should stop using it right now.

Nobody can give you wiser advice than yourself. - Cicero
.·´¯`·->Rajesh<-·´¯`·.
Codeproject.com: Visual C++ MVP

Cedric Moonen10-Apr-08 22:50

Cedric Moonen

10-Apr-08 22:50

What's the problem ?

Anyway, AFAIK, you can only check for equality on iterators (don't know if that is the case also on vector iterator). This your end loop condition should be:
myIntVectorIterator != myIntVector.end();

EDIT: I tested and you can do that with vector iterators (for list iterators, you can't). Anyway the problem is that you have to stop incrementing your iterator before the end of your vector. So replace <= by <. Otherwise, if you are at the end of your vector (not a valid element), you will still try to access the contents of the iterator (which is invalid).

Cédric Moonen
Software developer

Charting control [v1.3]

Jonathan [Darka]10-Apr-08 23:00

Jonathan [Darka]

10-Apr-08 23:00

You are going past the end of the iterator, change the code to something like this:

vector<int> myIntVector;

    // Add some elements to myIntVector
myIntVector.push_back(1);
myIntVector.push_back(4);
myIntVector.push_back(8);

vector<int>::iterator iStart = myIntVector.begin();
vector<int>::iterator iEnd = myIntVector.end();

while(iStart != iEnd)
{
    cout << *myIntVectorIterator << " "; //Should output 1 4 8
    ++iStart;
}</int></int></int>

Jonathan Wilkes
Darka[Xanya.net]

[My Code Project Articles]

after pressing button dialog box should be pop up like Windos Explorer Start Button in SDK [modified]

vikramlinux11-Apr-08 1:31

vikramlinux

11-Apr-08 1:31

Thanks for your suggestions guys !

Pankaj Kothawade10-Apr-08 19:48

Pankaj Kothawade

10-Apr-08 19:48

HI all,
i want to call a dialog box when i pressed a button which is at bottom side,the dialog box should be positioned on exact upper part of the button
how could i do dis?
plzzzzz help me

Pankaj

modified on Friday, April 11, 2008 6:36 AM

Re: after pressing button dialog box should be pop up like Windos Explorer Start Button in SDK

Hamid Taebi12-Apr-08 5:45

Hamid Taebi

12-Apr-08 5:45

You can use of DoModal or ShowWindow after you clicked button and then use of MoveWindow.

in-process server considerations

George_George10-Apr-08 19:39

George_George

10-Apr-08 19:39

Hello everyone,

Here is the comments from the book ATL Internals about in-process server considerations,

--------------------
Any thread that calls CoGetClassObject or CoCreateInstance must already have joined an apartment, or the call will fail immediately. So, does that mean all objects exposed from in-process servers must be equally at home in single-threaded and multithreaded apartments so that random clients isn't cause harm? Fortunately, no.
--------------------

Does it mean COM client (thread) and COM server no need to be the same type of thread model (e.g. STA, MTA, etc.)?

thanks in advance,
George

Stephen Hewitt10-Apr-08 20:14

Stephen Hewitt

10-Apr-08 20:14

George_George wrote:
Does it mean COM client (thread) and COM server no need to be the same type of thread model (e.g. STA, MTA, etc.)?

No. If the threading models are compatible direct communication occurs. If the threading models are incompatible the object is created in an apartment it can "live in" and the interface pointer is marshaled back to the caller -- communication occurs via a proxy and stub. This is one of COM’s key features.

Steve

George_George10-Apr-08 21:37

George_George

10-Apr-08 21:37

Thanks Steve,

How do you understand the quoted statements from my original question?

regards,
George

Stephen Hewitt10-Apr-08 21:39

Stephen Hewitt

10-Apr-08 21:39

I'm just going off my knowledge of COM.

Steve