combobox event in propertypage
-
stevy82 wrote: Since I do not have a derived CPropertySheet class... Why not?
"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown
-
Right, so I would have to handle the event in my CPropertySheet. Since I do not have a derived CPropertySheet class, I wish to handle it within the view class!
stevy82 wrote: Right, so I would have to handle the event in my CPropertySheet. Is the combo a child of the CPropertySheet or is in one of the property pages. If the latter, you can get the notification in your CPropertyPage derived class. -- jlr http://jlamas.blogspot.com/[^]
-
Let's say, I have to do it so. You understand? ;-) Okay, now is there a possibility to handle it in the view or not?
In the
CBN_SELCHANGEnotification handler, post a message to the view.
"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown
-
In the
CBN_SELCHANGEnotification handler, post a message to the view.
"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown
-
stevy82 wrote: Right, so I would have to handle the event in my CPropertySheet. Is the combo a child of the CPropertySheet or is in one of the property pages. If the latter, you can get the notification in your CPropertyPage derived class. -- jlr http://jlamas.blogspot.com/[^]
-
It is a child of a property page which is part of a property sheet. I do not have neither a derived sheet class nor a derived page class.
stevy82 wrote: It is a child of a property page which is part of a property sheet. I do not have neither a derived sheet class nor a derived page class. So, why don't you start writing a class derived from CPropertyPage? -- jlr http://jlamas.blogspot.com/[^]
-
stevy82 wrote: It is a child of a property page which is part of a property sheet. I do not have neither a derived sheet class nor a derived page class. So, why don't you start writing a class derived from CPropertyPage? -- jlr http://jlamas.blogspot.com/[^]
-
Because I was given the system in the way I mentioned and it is a demand not to create derived classes like that. Ain't it possible to handle the event within the View?
stevy82 wrote: Because I was given the system in the way I mentioned and it is a demand not to create derived classes like that. I have to wonder why anyone would impose such a restriction... stevy82 wrote: Ain't it possible to handle the event within the View? It might be, but it depends on what other restrictions you might have. Are you allowed to modify source files? Is it ok to write new code or are you only allowed to re-arrange the existing lines? ;P -- jlr http://jlamas.blogspot.com/[^]
-
stevy82 wrote: Because I was given the system in the way I mentioned and it is a demand not to create derived classes like that. I have to wonder why anyone would impose such a restriction... stevy82 wrote: Ain't it possible to handle the event within the View? It might be, but it depends on what other restrictions you might have. Are you allowed to modify source files? Is it ok to write new code or are you only allowed to re-arrange the existing lines? ;P -- jlr http://jlamas.blogspot.com/[^]
-
Of course, I'm allowed to write code ;) Which other restrictions (in fact there are no other restrictions than avoiding to create such sub classes) does it depend on? I just wonder how to get the CBN_SELCHANGE message passed to the view.
stevy82 wrote: Of course, I'm allowed to write code Oh, good! That's an start :) stevy82 wrote: Which other restrictions (in fact there are no other restrictions than avoiding to create such sub classes) does it depend on? Who is imposing that restriction? A silly restriction, if you don't mind my sincerity. Is this a real world program, or is it some sort of test? What's the reason for not wanting to derive the CPropertyPage? Please explain that. stevy82 wrote: I just wonder how to get the CBN_SELCHANGE message passed to the view. The easiest and logical way to do it is to derive the page, receive the notification there and pass it to wherever you want or need. It can also be done in other not so direct ways. For example, you might subclass[^] a window, either the combobox itself or its parent page, but perhaps that's against the rules too? -- jlr http://jlamas.blogspot.com/[^]
-
stevy82 wrote: Of course, I'm allowed to write code Oh, good! That's an start :) stevy82 wrote: Which other restrictions (in fact there are no other restrictions than avoiding to create such sub classes) does it depend on? Who is imposing that restriction? A silly restriction, if you don't mind my sincerity. Is this a real world program, or is it some sort of test? What's the reason for not wanting to derive the CPropertyPage? Please explain that. stevy82 wrote: I just wonder how to get the CBN_SELCHANGE message passed to the view. The easiest and logical way to do it is to derive the page, receive the notification there and pass it to wherever you want or need. It can also be done in other not so direct ways. For example, you might subclass[^] a window, either the combobox itself or its parent page, but perhaps that's against the rules too? -- jlr http://jlamas.blogspot.com/[^]
Jose Lamas Rios wrote: A silly restriction, if you don't mind my sincerity. You are right. Jose Lamas Rios wrote: Is this a real world program It is. Subclassing the combobox? Oh no. Well, I see I won't get it done within the view. I think I should rather occupy with the silly restriction than trying to find a solution. :doh:
-
Jose Lamas Rios wrote: A silly restriction, if you don't mind my sincerity. You are right. Jose Lamas Rios wrote: Is this a real world program It is. Subclassing the combobox? Oh no. Well, I see I won't get it done within the view. I think I should rather occupy with the silly restriction than trying to find a solution. :doh:
stevy82 wrote: I think I should rather occupy with the silly restriction than trying to find a solution Sounds like a good plan to me :) -- jlr http://jlamas.blogspot.com/[^]