|
From: WonderMan on 27 May 2008 06:42 Hans-J. Ude a �crit : > WonderMan <none(a)none.com> schrieb: > >> Hans-J. Ude a exprim� avec pr�cision : >>> WonderMan <none(a)none.com> wrote: >>> >>>> Well, my program is a small window, and has the Always-On-Top option >>>> set, so you cannot loose it ... >>> >>> If there is another Always-On-Top window it can be covered. Also if >>> the user clicks the show-desktop in Quick Launch it's gone. Maybe the >>> user clicked there accidentlay and will be confused now. If I have a >>> program and notice that it will take control out of my hand, that's a >>> program which very likely will be deleted soon. >>> >>> Hans >> >> What do you mean by : "if >>> the user clicks the show-desktop in Quick Launch it's gone" ? >> >> Can you tell me exactly how to do that (for a try) ? > > I have a german desktop environment so I'm not shure if I always use > the right terms but I'll try. The taskbar can have a quick launch > area. You can start a program with single click from there. It > contains a link to "C:\WINDOWS\Desktop anzeigen.scf" on my computer > which means as much "show desktop.scf" which sort of (not really) > minimizes all running programs even those without a minimize button. > When you click it again the desktop will be restored. > > HTH > Hans Thank you. I think I found the "Quick Launch" area (I work in a XP Pro machine) but did not find the link you mentionned ...
From: David Lowndes on 27 May 2008 07:14 >It is an "Always-On-Top" application, and it starts automatically when >Windows starts. So you're relying on the user being able to see your window and click on it - as others are pointing out, this is a bit of a false assumption. Dave
From: Doug Harrison [MVP] on 27 May 2008 11:04 On Tue, 27 May 2008 10:34:46 +0200, WonderMan <none(a)none.com> wrote: >Well, my program is a small window, and has the Always-On-Top option >set, so you cannot loose it ... You said earlier that there's "no possibility for the user to close it", which implies it runs forever. Combine this with Always-On-Top, and it seems like the end result will be more hateful than "helpful", especially for those people I mentioned (like me and Joe) who run maximized windows. Note that the jetToolbar program I described earlier has an Always-On-Top option, which was completely unhelpful to me and the first thing I disabled; it would be the first thing I disable in your program as well, which raises the "lost window" issue again. So far, it sounds like you're matching the jetToolbar design mistakes one for one, except that you're adding "impossible to close" to the mix. :) I really do mean that constructively, because as I explained, I had to go to some significant trouble to address those mistakes, and I would have given up on jetToolbar if I hadn't been able to figure out how to write a helper program to make it work acceptably. -- Doug Harrison Visual C++ MVP
From: AliR (VC++ MVP) on 27 May 2008 11:40 May I ask what not allowing the user to close the application has to do with hiding it from the taskbar? They are two entirely seperate problems. Also what about closing the appliation through the task manager? AliR. "WonderMan" <none(a)none.com> wrote in message news:mn.d3ce7d854b213587.88081(a)none.com... > Hello, > > I created a MFC dialog-based program with VC++ 6.0 and Windows XP Pro, but > when I use it, I get his name and icon showing on the Windows toolbar. > > Is there a way to hide the program from the Windows toolbar, i.e to be > able to use the program without having his name and icon displayed on the > Windows toolbar ? > > Thank you. > >
From: WonderMan on 27 May 2008 11:44
Doug Harrison [MVP] avait �crit le 27/05/2008 : > On Tue, 27 May 2008 10:34:46 +0200, WonderMan <none(a)none.com> wrote: > >> Well, my program is a small window, and has the Always-On-Top option >> set, so you cannot loose it ... > > You said earlier that there's "no possibility for the user to close it", > which implies it runs forever. Combine this with Always-On-Top, and it > seems like the end result will be more hateful than "helpful", especially > for those people I mentioned (like me and Joe) who run maximized windows. > Note that the jetToolbar program I described earlier has an Always-On-Top > option, which was completely unhelpful to me and the first thing I > disabled; it would be the first thing I disable in your program as well, > which raises the "lost window" issue again. So far, it sounds like you're > matching the jetToolbar design mistakes one for one, except that you're > adding "impossible to close" to the mix. :) I really do mean that > constructively, because as I explained, I had to go to some significant > trouble to address those mistakes, and I would have given up on jetToolbar > if I hadn't been able to figure out how to write a helper program to make > it work acceptably. Thank you for your interest and consideration, but I can assure you I know perfectly what I am doing, and there is a specific reason for which my program is being designed like this. I can not explain more as I hope this program will become a comercial program that will be sold on stores. However, I appreciate your concern and I'll think again on my project to find out if the ideas I used where as good as I think they are ... :-) |