|
MFC is a set of classes used for Windows programming, not a design pattern.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
Exactly, its a framework, but on the other hand I saw some books that mentioned the document-view "design pattern" and some other similar stuff about MFC.
|
|
|
|
|
It's a long time since I read anything about MFC, maybe it is offering more than when I worked with it.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
Same sh.t with some new stuff like ribbon. I see it in action regularly in old progs. Unfortunately legacy stuff keeps this beast alive and more or less updated.
|
|
|
|
|
MFC is a deprecated framework. Don't invest time in learning it unless you have to maintain legacy systems written in it. MFC is not just a GUI library, its a set of classes for a lot of other problems too but ppl are using MFC mainly as a C++ gui framework. Unfortunately I can't recommend a really good C++ gui library for you but Qt is definately a much better solution because its much more object oriented than MFC and its crossplatform. MFCism is a religion coming from the previous century, avoid it if its possible.
EDIT: I see there are some downvoter MFC fans here, but they are afraid to show their names and opinions... :P
modified 31-Jul-12 15:50pm.
|
|
|
|
|
MFC is not a deprecated framework, agreed that there are sections of it that are and always have been useless (all the collection classes), but it is still worked on and still offer good bang for the money for classic and modern application designs, especially when working with C++.
(I did not vote you up or down).
Watched code never compiles.
|
|
|
|
|
The design of the gui part is deprecated, and would say that its only half C++. I'm talking about gui because thats part is the most widely used from MFC. Among the helper classes I think there is some useful stuff but don't use them anymore because of crossplatform development. You can say "it works" even about the worst library of the world, its never a good reasoning. Its cost is zero if I'm right if you bought visual studio, but buying even the most expensive gui library is usually only a fraction of the development of a software. Of course you can put together nice gui in MFC, but its more difficult than doing the same with a better system. Not to mention the maintaining of the code, especially if a lot of ppl are working on it, and not all of them are MFC experts. You might be very good at it for now, but imagine how many things you must be aware of to handle MFC well: Win32 dialog resources, subclassing/hooking, window messages to some degree, etc... Its not a small piece... And its not just C++! A good gui library gives you a pure nice C++ interface.
EDIT: Its no problem to downvote something, the '1' button is there for this reason! 
|
|
|
|
|
[This] article discusses what a Design Pattern is, classification of Patterns, and MFC and Design Patterns.
More on Design Patterns [here].
|
|
|
|
|
Hi,
I need to draw a spikey 3D surface plot. It might include 300 x 500 points along the horizontal x and y axes and the height (z-axis) might be an integer between 0 and 100. I want the hight to be represented by colour banding...i.e. a point at the front of the graph with a value of 100 would be a tall bar going from green through brown through orange through to white at the top. And a value of 50 would only be a bar with green through to brown.
The most simple (and hopefully effective) solution I can think of is to draw a vertical bar for each point, rather than any triangle drawing as Excel does for it's surface plot.
My question is...how can I do this quickly? I'd do some vector maths to skip any points that don't need to be drawn (hidden bars) and merge others that sit on the same pixel, but could still have 1-2000 points to draw! So would it be possible/quicker to use a cached bitmap of a single full height bar and just copy a portion of it (depending on the z-value) onto a memory dc 2000 times or to use GDI+ and draw 2000 gradient lines/bars? I've not used GDI+ so am trying to work out which bit of darkness to stumble into and read up on!
Any thoughts/suggestions/relevant articles would be hugely appreciated.
Thanks,
Phil.
|
|
|
|
|
A excel class control does help ? This class can programatically draw 3d charts ... if could help you, I'm glad to send it to you ...
|
|
|
|
|
Hi Flaviu2,
Does the class output data to Excel and draw a surface plot within Excel? If so, thanks, but I've already implemented this as an interim measure. I actually need to do the drawing within an MFC application, so various settings can be modified and the results updated in real time.
Otherwise, if your class draws 3d charts within an MFC view, that would be awesome - yes please!
Many thanks,
Phil.
He is no fool, who gives what he cannot keep, to gain that which he cannot lose.
|
|
|
|
|
This class could control excel graph in two way : like excel ActiveX object inside of an MFC application or, could control an excel graph in new created file, in exterior of an MFC application but with control from inside of MFC application ... if you say that could help you, I will gladly give you ... and more, I will try to make a little demo ...
|
|
|
|
|
Ah, using Excel in as an ActiveX object is an interesting idea, so yes please, I'd love to see a little demo. Thanks!
|
|
|
|
|
Please send me an email ...
|
|
|
|
|
Following is the code which i wrote to implement a splitter view to join together 5 dialog. Problem is the split window at the bottom screen occupies the whole form area please help me to remove the error.
BOOL CMainFrame::OnCreateClient(LPCREATESTRUCT lpcs, CCreateContext* pContext)
{
m_wndSplitter.CreateStatic(this, 2, 1);
m_wndSplitter2.CreateStatic(&m_wndSplitter, 1, 2, WS_CHILD | WS_VISIBLE, m_wndSplitter.IdFromRowCol (0, 0));
m_wndSplitter2.CreateView(0, 0, RUNTIME_CLASS(CFormLeft), CSize(200,100), pContext);
m_wndSplitter1.CreateStatic(&m_wndSplitter, 1, 2, WS_CHILD | WS_VISIBLE, m_wndSplitter.IdFromRowCol (1, 0));
m_wndSplitter1.CreateView(0, 0, RUNTIME_CLASS(CFormBottomLeft), CSize(200,100), pContext);
m_wndSplitter1.CreateView(0, 1, RUNTIME_CLASS(CFormBottomRight), CSize(200,100), pContext);
m_wndSplitter3.CreateStatic(&m_wndSplitter2, 2, 1, WS_CHILD | WS_VISIBLE, m_wndSplitter2.IdFromRowCol (0, 1));
m_wndSplitter3.CreateView(0, 0, RUNTIME_CLASS(CFormRightUp), CSize(200,100), pContext);
m_wndSplitter3.CreateView(1, 0, RUNTIME_CLASS(CFormRightBottom), CSize(200,100), pContext);
return TRUE;
}
|
|
|
|
|
I believe you need to create views for all the panes that you create.
So after you create a splitter with m_wndSplitter having 2 rows, you need to create 2 views in these 2 rows before creating the next splitter with m_wndSplitter2.
|
|
|
|
|
Does [this] article help?
|
|
|
|
|
Yup it helped.
But actually what i did was to resize the dialog boxes after all the splitter controls were created.
|
|
|
|
|
Hi all,
i want to know how can i save my CTreeCtrl Structure in a file ,and again load same a previous from reading the save file.
thanks.
|
|
|
|
|
See my answer to your other question. Alternatively you could learn about the CFile class and roll your own.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
Again, once you have grasped the MFC serialization fundamentals (please see the link to the documentation I provided in the below thread), you'll find yourself how to serialize the CTreeCtrl object.
Veni, vidi, vici.
|
|
|
|
|
Why file? Thats so Windows 3.11's win.ini
Do it in the registry.
But here you go.
|
|
|
|
|
Actually serialization has (almost) nothing to do with .ini files and it still a well-alive technique (one may argue that .ini files too are still used).
Veni, vidi, vici.
|
|
|
|
|
Again you are always right.
The Wiki page states:
Serialization is the process of converting a data structure or object state into a format that can be stored (for example, in a file or memory buffer, or transmitted across a network connection link) and "resurrected" later in the same or another computer environment.
http://en.wikipedia.org/wiki/Serialization[^]
The INI file format is an informal standard for configuration files for some platforms or software. INI files are simple text files with a basic structure composed of "sections" and "properties".
http://en.wikipedia.org/wiki/INI_file[^]
|
|
|
|
|
TopCoder23 wrote: Again you are always right.
May I forward your sentence to Mrs 'The Wife'?
Veni, vidi, vici.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
