I was talking about a microsoft team implementation...i saw some resize helpers around here somewhere but none of them do what i need them to do. It's a bit frustrating 'cause when you're developing some huge application with complicated non gui processes, the last thing you want to focus on is layout. And don't talk to me about the Dialog editor that ships with the .net platform...not everything can be done by mouse clicks
I just started working on this, so any suggestions would be helpful. I have a program that transfers files to and from a CDMA cell-phone chip simulation board. Essentially, a cell phone connected to the PC via a USB cable. The files on the phone are displayed in a GUI, and the program itself transfers the files via programmer-defined packets. The GUI itself is a high-level layer on top of pre-existing firmware level application, which actually controls the phone with transmission/receive messages. I would like to make the GUI a drag and drop application, where the files in a given directory are listed in a listbox on a form, and to transfer files to/fro one can merely drag and drop files in and out of the list box to location designated in the PC. I have looked at implementing drag and drop for files on PC's with MFC, but it seems it's all done with the assumption that the files are all located in files on a PC or a PC-based network. The transfer process itself can take minutes for mp3 files. Does anyone have any thoughts on implementing a shell drag and drop process which will emulate the PC process but the actual transfer of data is done with the pre-existing firmware code.
I am working on a simple program that must load a bitmap and then resize the window that the bitmap is displayed in so that it is the exact size of the bitmap. The program appears to work fine, except for one small problem. When Windows redraws the window that has now been resized, the border on both the right hand side and the bottom do not get drawn. Also, it appears that the orignal "X" box that closes the program is still there. However, if I resize the window manually after the computer has redrwan the window, both borders appear and the old "X" box disappears. Anyone have any idea how I can go about fixing this problem?
SetWindowPos has a flag to indicate that the non-client area of the window needs updating. You can either use SetWindowPos to do the resize (if you are not already using SetWindowPos), or you can do something like the following just to force the frame to redraw:
// Put this after your call to MoveWindow or whatever
SetWindowPos( Your_HWND_Here, NULL, 0, 0, 0, 0, SWP_NOMOVE | SWP_NOSIZE | SWP_NOACTIVATE | SWP_NOZORDER | SWP_DRAWFRAME );
It's a hWnd for a window. I've tried to use SetWindowsHookEx and LoadLibrary, but they do not seem to do anything. I don't know if I am using them quite right or not, or either SetWindowHookEx is only used for mouse and keyboard hooking or what. Maybe hooking applications is too advance for SetWindowHookEx. I really dunno.
Yes, it have used it. But I used FindWindowEx instead. It retrieves the hWnd of a window based on the class name for that particular application. That is a piece of the puzzle but not the whole thing. Now, I'm trying to use that hWnd and SetWindowsHookEx to hook it to that particular window, but I'm having no luck.
Abu Mami's Easy Installer files that I downloaded DID NOT include any ".clw" or ".dsw" or ".dsp" files. can someone send them to me. Also, how are you to compile the Easy Installer or change some of the coding without being able to load it into the IDE (using VS 6.0)
A C++ programming language novice, but striving to learn
I need do open a "please wait" window in order to keep blocked my MFC application (i mean that the user can do nothing) until a time-expensive routine ends. Then i need to close this "please wait" window.
I need a modal dialog i suppose.
How can i do that ?
Should i launch the time-expensive routine from the modal dialog ?
All you need to do is create a new dialog window, open it before runnning your expensive routine and close it after. In my opinion, having a "please wait" and forcing your user to sit there twiddling there thumbs is bad programming. Why not use a thread instead?
Because the user knows he has to wait so long and he wants the results that can be shown only AFTER the computation in the routine.
( The routine i'm talkin' about is a multi-objective genetic algorithm that finds a pareto-front of
solution after searching the causative bodies of seismic/volcanic effetcs)