You can do that manually by converting dialog to doc-view based SDI/MDI app by creating new Doc,View,Frame files and integrating the logic in there and doing lots of other things. But that would be very cryptic because there are very meticulous things to be done in order to achieve it.(e.g. manually editing RC to create frames, menu, toolbar and all).
I think instead of tweaking same app from dlg based to SDI/MSI, it'd be better if you create a fresh MDI/SDI app and then port the functionality one by one from your dialog based app to the SDI/MDI app.
Well if you implemented any sort of Design using Best Practices and Patterns it should be very simple rote work to replace the UI with another. Of course you have to actually develop the UI which may not be simple at all.
I want to launch command prompt window from my application running on Windows Vista. For this purpose i am using CreateProcess. What i want is that command prompt window shoul be launched with Administrative priviliges. Please tell me how can i do so ?
I would really like to use CWinThread class.
I have an odd situation where i am in a dll and would like to use a thread. For come reason CWinThread is not accessible here.
When i try to inclde afxwin.h before my stdafx.h
I would not compile on :
I get the following errors
error C2143: syntax error: missing ';' before'*'
error C2501: 'CWinThread':missing storage-class or type specifiers.
How would i get around this using a Win32 dll trying to implement an MFC class like CwinThread? If this is not possible, what are my thread options. I am simply creating a waitable timer but wanted to do this in a thread.
I have a requirement , where I want one entity to be persistent in the computer.
I am struggling to decide on what this entity will be .
My model is such that I want to be able to intercept USB device notifications utilizing the WM_DEVICE_CHANGE messages by creating a hidden window in this entity and then update the elements of a system tray icon ( which exposes a Menu ) .
So my requirement does not fit the Client Server model , yet I am leaning towards COM to provide one EXE that does it all . So in other words , this entity will not provide any APIs for other clients to use . Am I unnecessarily using COM ?
So finally I need to finalize the form that this need to take .
Service - actually the Visual Studio 6 gives the option to create a COM Object as a Service.
Standalone EXE ?
Your inputs are really appreciated
Engineering is the effort !
Last Visit: 31-Dec-99 18:00 Last Update: 27-Sep-23 0:05