Mfc Profile Layout Codes

Mfc Profile Layout Codes

Table of contents

Exit focus mode

Light

Dark

High contrast

Light

Dark

High contrast

This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
This topic provides tips for customizing an MFC application.
You can save and load the state of your application to the registry. When you enable this option, your application will load its initial state from the registry. If you change the initial docking layout for your application, you will have to clear the registry data for your application. Otherwise, the data in the registry will override any changes that you made to the initial layout.
Additional customization tips can be found in the following topics:

Sign up or log in to customize your list.

more stack exchange communities

company blog

Stack Overflow for Teams
– Start collaborating and sharing organizational knowledge.

Create a free Team
Why Teams?

Asked
7 years, 3 months ago

Modified
7 years, 3 months ago

2,947 4 4 gold badges 28 28 silver badges 48 48 bronze badges

Highest score (default)

Trending (recent votes count more)

Date modified (newest first)

Date created (oldest first)

2,947 4 4 gold badges 28 28 silver badges 48 48 bronze badges

3,794 1 1 gold badge 17 17 silver badges 26 26 bronze badges

137k 11 11 gold badges 113 113 silver badges 232 232 bronze badges

Stack Overflow

Questions
Help

Products

Teams
Advertising
Collectives
Talent

Company

About
Press
Work Here
Legal
Privacy Policy
Terms of Service
Contact Us
Cookie Settings
Cookie Policy

Stack Exchange Network

Technology

Culture & recreation

Life & arts

Science

Professional

Business

API

Data

Accept all cookies

Customize settings

Find centralized, trusted content and collaborate around the technologies you use most.
Connect and share knowledge within a single location that is structured and easy to search.
I understand there are functions that can easily write windows registry, however I found out that in new MFC project created with wizard, some information (like split bar position, visibility of controls) gets stored automatically (or at least I found no CWinApp::Write* calls in the project). Since I have also older projects that don't have this behaviour I need to figure out how to make this without help of project wizard. Would anyone please know how does this work?
Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.
It falls back to sorting by highest score if no posts are trending.
The MFC control state saving magic happens in the 'New' MFC Feature Pack , specifically in the SaveState methods, for example CMFCToolBar::SaveState .
To take advantage of this you'll therefore need to upgrade your Toolbars and Menus to use the newer controls and upgrade your application to inherit from CWinAppEx . I recommend that you use a New MFC Wizard based app as a guide on how to upgrade your old MFC app.
Most of the information is saved in CPane::SaveState(), thus if you want state of some component saved, you need to use classes derived from CPane. (for more info here is the class hierarchy).
The process of saving window states is initiated through CFrameImpl::OnClosingMainFrame(). This function in turn calls CWinAppEx::SaveState() which saves some application settings and then ALL instances of CMFCToolBar (they add themselves to global list of CMFCToolBars in call to OnCreate). In a similar way all dockable panes are saved but the list belongs to your main frame. Then positioin and size of your main frame is saved.
CViews and CFrameWnds are somewhat less favored, for what I found and tried out, the only information saved was visibility.
I used that loooong time ago. If I correctly reminds it, you should save the informations you want in a overridden CWinApp::ExitInstance() before calling base class method, and you load them in CWinApp::InitInstance . Be sure to allow for default values, because at first run, there will be nothing to load, and do not forget to call (or copy) base class.
Thanks for contributing an answer to Stack Overflow!

By clicking “Post Your Answer”, you agree to our terms of service , privacy policy and cookie policy

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

Site design / logo © 2022 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2022.8.11.42805

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy .

Search within:

Articles
Quick Answers
Messages

Please Sign up or sign in
to vote.

Templates are a great way of reusing code, unfortunately MFC makes it hard to write MFC friendly template classes...

Software Developer (Senior)
JetByte Limited

Len has been programming for over 30 years, having first started with a Sinclair ZX-80 . Now he runs his own consulting company, JetByte Limited and has a technical blog here .

JetByte provides contract programming and consultancy services. We can provide experience in COM, Corba, C++, Windows NT and UNIX. Our speciality is the design and implementation of systems but we are happy t ...

Len has been programming for over 30 years, having first started with a Sinclair ZX-80 . Now he runs his own consulting company, JetByte Limited and has a technical blog here .

JetByte provides contract programming and consultancy services. We can provide experience in COM, Corba, C++, Windows NT and UNIX. Our speciality is the design and implementation of systems but we are happy to work with you throughout the entire project life-cycle. We are happy to quote for fixed price work, or, if required, can work for an hourly rate.

We are based in London, England, but, thanks to the Internet, we can work 'virtually' anywhere...

Please note that many of the articles here may have updated code available on Len's blog and that the IOCP socket server framework is also available in a licensed, much improved and fully supported version, see here for details.

You must Sign In to use this message board.

Spacing
Relaxed Compact Tight
  Layout
Normal Open Topics Open All Thread View
  Per page
10 25 50


Free C++ libraries with source code on www.neatcpp.com : TWAIN, DirectShow, Interprocess Communications, etc...
Len Holgate
www.jetbyte.com
The right code, right now.

Len Holgate
www.jetbyte.com
The right code, right now.

Christopher Stratmann 23-Mar-06 1:40

Article Copyright 2000 by Len Holgate Everything else
Copyright © CodeProject , 1999-2022

Web03
2.8.2022.07.15.1

Templates are cool. Being able to write code that can work on objects of any type that satisfies the minimum functionality that you require, make reusing code considerably easier. No more type-unsafe generic coding methods, like void * 's and macros. Templates solve all manner of problems.
Using templates with MFC classes, especially MFC classes with message maps, isn't easy. Why would you want to do so? Well, how about a class derived from a list box that can manage the lifetime of the objects displayed in it? You could put items into the list and store pointers to them in the item data and when the box is destroyed, it can clean up and delete the objects for you. One problem with this is that at the point where the list box deletes your object, it only has a void * pointer to it. Calling delete on that pointer wont call the object's destructor.
Luckily, although you have to jump through a few hoops, it's not that difficult to make MFC classes work with templates. The main problem are the message map macros.
If you look at the standard BEGIN_MESSAGE_MAP macro, you can see the problem:
If the class you're declaring a message map for is a template class then the macro expands all wrong... The template bits are missing. What you really need is something more like this....
The macro above recognizes the fact that the class is a template and puts the template bit in the right places.
where TListBox<> is the derived class you're setting up the message map for, CJBListBox is the base class and the bit is what ever is appropriate for your template definition.
When it comes to implementing the handler, you do it in the usual way...
And because you KNOW the type of object that you're storing in the list box's item data ptr, you can implement DeleteAll() like this:
Of course, it's not quite that easy. The class wizard often goes nuts when it sees these classes, so it's best to fully implement the class for a particular data type before you turn it into a template. Alternatively, keep the original class wizard macro to hand, and just comment it out when you don't need to do class wizard stuff.
If you comment the Template version out and uncomment the standard version, then you can add more message handlers using class wizard. Then you should switch the comments and adjust the generated code to suit.
Since there are different versions of the message map macros for when _AFXDLL is defined and when it's not, the full code required is as follows:
The sample code shows this in action. First we define a list box that knows how to manage the lifetime of objects within it, then we derive another template class from it that knows how to populate itself from an STL style iterator that's passed to its constructor.
While I was tidying up the example code, I realized that I needed a template class in the form:
Of course, as soon as I put this into the macro, it broke... The problem is that the comma required between the part of the template becomes two macro parameters... I quickly wrote a quick fix, a macro that explicitly took the extra template parameter. The problem was that this was ugly (I now had 2 template message map macros) and it wasn't extensible. (If I needed a template with 3 parameters, or if the base class needed multiple template parameters, I had to change the complex macro to cope.) At around this time, I saw the message on the guest book from Dave Lorde mentioning a similar problem...
After some thought, it became obvious that the problem could be solved by another level of indirection. I added the following simple macros to the top of the header file and removed the extra message map macro:
The message map macro needed one final change (including the <>'s for the initial template declaration)...
Now you can use the macro as follows:
wrapping multiple template parameters in the appropriate macros before use. The main message map macro never needs changing, if you need more parameters just add another simple macro pair to the top of the file. What's more, these macros can be used when the base class has multiple parameters too!
When the dialog is initialized, the list is created and passed the iterators it needs. There's a horrible hack in here so that when it gets its first message (and we know the actual window exists!), we populate the list box from the iterators. When the box is destroyed, we clean up. If anyone knows a better way to tell when a window has been created and actually exists so we can send messages to it, please tell me!
The nice thing about the code presented is that it can be used for any kind of object that can be iterated over by an iterator. The sample shows the same code being used for a list of GUIDs in the registry and a list of GUIDs obtained from the component category manager.
See the article on Len's homepage for the latest updates.
This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)
General  News  Suggestion  Question  Bug  Answer  Joke  Praise  Rant  Admin
Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.
.h file:

template
class CSpinTmpl :
public CSpinButtonCtrl
{

DECLARE_MESSAGE_MAP()

public:
CSpinTmpl(){};
~CSpinTmpl(){};

protected:

public:

afx_msg void OnDeltapos(NMHDR *pNMHDR, LRESULT *pResult)
{
LPNMUPDOWN pNMUpDown = reinterpret_cast(pNMHDR);
// TODO: Add your control notification handler code here
*pResult = 0;
};

};

.cpp file

#define TEMPLATE_1(t1) t1
#define TEMPLATE_2(t1, t2) t1, t2
#define TEMPLATE_3(t1 ,t2 ,t3) t1, t2, t3

#define TCLASS_1(theClass, t1) theClass
#define TCLASS_2(theClass, t1, t2) theClass
#define TCLASS_3(theClass, t1, t2, t3) theClass

#ifdef _AFXDLL
#define BEGIN_TEMPLATE_MESSAGE_MAP(theTemplate, theClass, baseClass) \
template const AFX_MSGMAP* PASCAL theClass::GetThisMessageMap() \
{ return &theClass::messageMap; } \
template const AFX_MSGMAP* theClass::GetMessageMap() const \
{ return &theClass::messageMap; } \
template AFX_COMDAT const AFX_MSGMAP theClass::messageMap = \
{ &baseClass::GetThisMessageMap, &theClass::_messageEntries[0] }; \
template AFX_COMDAT const AFX_MSGMAP_ENTRY theClass::_messageEntries[] = \
{ \

#else
#define BEGIN_TEMPLATE_MESSAGE_MAP(theTemplate, theClass, baseClass) \
template const AFX_MSGMAP* theClass::GetMessageMap() const \
{ return &theClass::messageMap; } \
template AFX_COMDAT const AFX_MSGMAP theClass::messageMap = \
{ &baseClass::messageMap, &theClass::_messageEntries[0] }; \
template AFX_COMDAT const AFX_MSGMAP_ENTRY theClass::_messageEntries[] = \
{ \

#endif

BEGIN_TEMPLATE_MESSAGE_MAP(TEMPLATE_2(class GubiciGabariti, class Jezgro),
TCLASS_2(CSpinTmpl, GubiciGabariti, Jezgro), CSpinButtonCtrl)
ON_NOTIFY_REFLECT(UDN_DELTAPOS, OnDeltapos)
END_MESSAGE_MAP()

First error in the list:
messageMap' : is not a member of 'CSpinTmpl
I'm just thinking if typedef can solve the problem?
use typedef and then use MFC message map macroes as usual?
template class TImageCollectionListCtrl : public TCollectionListCtrl

BEGIN_TEMPLATE_MESSAGE_MAP(TEMPLATE_2(class T, class TI),
TCLASS_2(TVehicleCollectionListCtrl, T, TI),
TImageCollectionListCtrl)

? I get a too many parameters error
Thank you so much for providing this code. I was able to finally create a template dialog.

Chris
I used the latest version of the original macro from afxwin.h and made the appropriate modifications.

#ifdef _AFXDLL
#define BEGIN_TEMPLATE_MESSAGE_MAP(theTemplate, theClass, baseClass) \
template const AFX_MSGMAP* PASCAL theClass::GetThisMessageMap() \
{ return &theClass::messageMap; } \
template
Innocent Doll Mfc
Pokemon Lusamine Porn
Dbz Porn Manga

Mfc Profile Layout Codes

Report Page