[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 981
  • Last Modified:

CFormView, CDialog, and events...

Environment:  VC++ 5.0 and Windows NT 4.0

Hello everyone,

I'm creating a CFormView based MDI application and have created a CDialog based class to handle the processing for the dialog itself.  My question involves the handling of events.

If I add an event handler (for a button on the dialog for example) to the CDialog based class, I don't seem to be able to receive notifications from the button.  However, if I place the event handler in the CFormView based class, I can
receive the event from the button.

Is there any way to have the CDialog based class handle the events without manually passing the events to the class thru the CFormview based class?

Any suggestions would be helpful.

Thanks in advance,
Mike Irvin
M.Irvin@Dialogic.com
0
irvinm
Asked:
irvinm
  • 2
  • 2
1 Solution
 
davmarcCommented:
Controls included in your CDialog window send notification messages to their parent - the CDialog.

Controls included in your CFormView window send notification messages to their parent - the CFormView.

If you want someone else CDialog to handle CFromView controls notification messages (or vice versa) you must forward the messages manually.

Davide Marcato.
0
 
Amaresh080997Commented:
Hi MikeIrvin,
I dont clearly understand your requirement.As far as I understand  ur requirement, I think u may have to pass the messages manually.

0
 
irvinmAuthor Commented:
I am a little confused over the concept of having a CDialog
class handling the controls in the dialog.

In my application I am trying to separate the CView (CFormView)
from the processing and event handling in the CDialog.  When
I add an event processor in the CDialog to handle the events
from the controls in the dialog, I can not receive events.

However, if I move the event handling to the View class,
everything is fine.  So, from your explaination, events from
the Dialog controls should be routed to the parent (which
makes sense), but since that is the CView, what is the point
of creating a separate class (CDialog) based to handle the
processing when events have to be manually route to this
class.

Doesn't it make sense to place the processing of dialog controls
into a CDialog class for encapsulation purposes.

Thanks for the initial information,
Mike Irvin
0
 
davmarcCommented:
The rule is that every control sends notification messages to its parent, being it a CView window or a dialog box.

I think you are making some confusion about the role of CFormView: it seems like a dialog box and internally behaves mostly like that, but it is managed by a CView derived class to make it fit into the document/view paradigm as MFC implements it.

When you work with a CFormView, most of the concepts valid for regular (modeless) dialog boxes apply as well: you place the controls with the resource editor, you handle the messages coming from them, and so forth.
But you implement everything in your customized CFormView-derived class, without dealing with CDialog at all. You use CDialog only for working with traditional non-document/view non-CFramed dialog boxes.

I hope this explanation helps somehow.
After associating a CDialog-derived class with a dialog template,  the messages generated by its controls will be delivered to class' handlers. Otherwise, there is something incorrect in your code.

Davide Marcato.
0
 
irvinmAuthor Commented:
Thank you for the explaination.
0

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now