The row stays selected and is highlighted - but the highlighting changes colour when the control loses focus - I don't believe there's nything you can do about that without making the control owner-draw.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
Recently,I have to design a small soft,but how to make the software interface on our own style is beyond us.As we all known, the window created by MFC is very ugly.Some software interface is so attractive,but how to imatate?(English is not my mother language and this is my first time ashing question,I am sorry I can't declared my doubt clearly.)
Use Adobe Photoshop to make custom defined bitmaps of whatever design you want and paste it onto the dialogs during initialization + OnPaint handlers. Simple!
There are numerous code samples available on this site.
I am using VC++ MFC control.I am having a form which contains a combobox,a listbox and button..now I hv few text files say for example abc.txt,cdf.txt and so on..Now if I select a particular name say abc from combobox all the parameter names which is in that file "abc.txt" will automaticaly get displayed in the listbox.Each file has a parameter number ,name and value,so while displaying the parameter names I have used indexes.
So the format stored in the text file is as follows:
index no 0
parameter no1 4
parameter name1 fdf
paramter value1 A3434
index no 1
parameter no2 7
parameter name2 eter
paramter value2 B3565
and so on..
These values are copied into these text files from a particular text file
which contains parameter no,paramter name and parameter value without index numnber.I hv used it for displaying names on the listbox.
So my doubt is:
How to display the list of parameter names of each text file whenever the file is selected using combobox on the list box without using the index numbers.I dont want to use it since it takes extra space in the file.Is there anyway to do this?Please suggest me and help...
I am currently writing a program that will be running on an XP-embedded machine that will act as a watchdog and launcher of another application. Naturally, since this needs to be persistent on the machine, it makes since to write it as a windows service. However, I'm not sure what benefits this will have over a standard application because I have not had a great deal of experience writing services. For one, these machines will never be touched by end-users so an application running in the taskbar would not have the problem of an accidental closure or user error. Two, this program may require relatively constant communication with the application it opens and know if it dies so it can report back to a central server, as well as status update to said server.
So I guess my overall question is are there any caveats to writing this as a windows service? Is there any performance gain or loss when it comes to messaging between the applications? Any opinions and thought are greatly appreciated.
I work on XPe and we do everything quite deliberately as applications, not services. The only real benefit a service has is the built in ability to be restarted by the service manager. Our solution is make sure our "services" don't crash. (Some of our services can't really be restarted anyway
On the negative side, services are annoying to debug (when problems happen when in service mode) and maintain in an XPe environment. In our case, we push down updates, the machine reboots and the updates are xcopy installed. Can't do this with services.
Anyone who thinks he has a better idea of what's good for people than people do is a swine.
- P.J. O'Rourke