Re: CPropertySheet/Page

Tech-Archive recommends: Fix windows errors by optimizing your registry

Wrong approach.

Instead, treat the parent of your property pages as a "document:" and the property pages
as "views". In the OnKillActive of each page, you store into variables of the parent the
values you want other property pages to see. In the OnSetActive of a page, you retrieve
these values. PSM_QUERYSIBLINGS is almost totally useless.
joe

On Wed, 13 Dec 2006 13:44:42 -0500, "Bob" <bsagusti@xxxxxxxxxxx> wrote:

Hello,

I am creating a dialog app but the info that I must handle requires more
space than just one dialog. I decided to go with a property ***, that way
I can convey data to the user in a non-cluttered, orderly fashion. The first
prop page gets data from a socket and elements of that data is to be
displayed on all the pages. I'm using QuerySiblings() to notify the other
pages and pass a pointer to the data.

My problem is that unless the user clicks the tabs to cause InitDialog() to
be called on the other property pages, the PSM_QUERYSIBLINGS message is not
sent to those pages. I need the data to be in the controls of those property
pages when the user clicks on them the first time.

Is there a way to cause InitDialog() to get called? i.e. some way to cause a
WM_NOTIFY?

Am I going about this wrong?

Thanks a lot.

Bob

Joseph M. Newcomer [MVP]
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.

Quantcast