Prev: Derived Class at Design Time
Next: Control color skin
From: Joseph M. Newcomer on 26 Apr 2010 01:07 Actually, most of my dialog-based apps are delivered as products. joe On Sun, 25 Apr 2010 19:07:57 -0400, Hector Santos <sant9442(a)nospam.gmail.com> wrote: >Hi Joe, "see below" <g> > >Joseph M. Newcomer wrote: > >> Probably 80% of the apps I write are dialog-based apps. There are small and subtle >> differences between an dialog-based app and an SDI app with a CFormView; for example, the >> SDI app has a status bar while the dialog-based app normally doesn't (but it can be >> added). But overall most of the people don't seem to care about the distinctions. >> >> I did one app that I thought "should" have been a dialog-based app, but I did it as MDI >> mostly because we wanted multiple views/ Turns out we needed to handle multiple devices, >> so when the client called and asked for it, all I did was disable the code that allowed >> only one document at a time to open. Took maybe 2 minutes. I emailed the solution 20 >> minutes later (I did a little testing) >> >> I also suggest that for learning MFC, dialog-based apps are often a better choice for a >> beginner. >> >> joe > > >But you "can't" always do this for commercial software or for software >served more than one person. In my experience, a good bit of the time >it is spur of the moment thing where one customer is doing something >at a particular and RARE moment and says "Geez, wouldn't it be >nice..." and makes the suggestion, but then it isn't needed 99% of the >time or even ever again. Many times no one follows up. It would be a >major mistake to believe silence means agreement. In fact, in many >circles silence could mean no interest in the suggestion. Joseph M. Newcomer [MVP] email: newcomer(a)flounder.com Web: http://www.flounder.com MVP Tips: http://www.flounder.com/mvp_tips.htm
From: Joseph M. Newcomer on 26 Apr 2010 01:11
What I did was replace the File>New with two of my own menu items: New Configuration File and New Controller. And the File Open uses document templates to allow .cfg files to be read in as either configuration-files-to-be-edited or configuration-files-to-map-to-a-remote-machine. I pushed a lot on how the logic within MFC works, and the file open dialog has an "Open As" dropdown, to select which mode to use and consequently determine on-the-fly which type of document to create. I don't use the built-in mechanisms at all, because they don't do the right thing. joe On Sun, 25 Apr 2010 17:50:51 -0700 (PDT), Jd <j.durgaprasad(a)gmail.com> wrote: >On Apr 22, 11:14�pm, Joseph M. Newcomer <newco...(a)flounder.com> wrote: >> Actually, I did this some years ago. �The "config" file was an external file that >> specified the properties of a remote embedded system. �The other type of documeht actually >> communicated to a remote embedded system. >> � � � � � � � � � � � � � � � � joe >> >> On Thu, 22 Apr 2010 03:27:46 -0700 (PDT), Goran <goran.pu...(a)gmail.com> wrote: >> >On Apr 21, 4:56�pm, Joseph M. Newcomer <newco...(a)flounder.com> wrote: >> >> What the OP is asking is how to have an app that allows for either of two types of >> >> documents to be created, at the user's request, instead of creating only one type of >> >> document by default. �The techniques discussed earlier are what are required. >> >> � � � � � � � � � � � � � � � � � � � � joe >> >> >Well, it doesn't seem so. � understood it as needing to modify a >> >config file for the whole app (some kind of "options" command an such) >> >- happens all the time. It's an overkill to introduce another doc type >> >for that. >> >> >Goran. >> >> Joseph M. Newcomer [MVP] >> email: newco...(a)flounder.com >> Web:http://www.flounder.com >> MVP Tips:http://www.flounder.com/mvp_tips.htm > >Dear Joe, >Sorry , I was sick and couldn't follow up the thread. >My app is almost same as the one you mentioned. >A config file to specify the properties of a remote embedded system. >( this part is used rarely, as it is a complex system and >configuration changes very rarely) and transfer the config file to the >system. > >And the other part is monitoring the system and the devices attached >to the system. > > >Jd > > Joseph M. Newcomer [MVP] email: newcomer(a)flounder.com Web: http://www.flounder.com MVP Tips: http://www.flounder.com/mvp_tips.htm |