It crashes when doing the actual function call? Hmmm ... Can you call anything in the DLL? Try calling a function returning void with no arguments, to eliminate problems with calling conventions and stuff like that. Does DllMain get called properly?
I want to be able to disable the UI for an ActiveX control while certain processing is happening. Is there a way to "gray-out" the entire control without having to disable each individual button or field in the control?
Processing will be done on a background thread, and in most cases, I do wish to maintain a responsive UI. But in some cases, I need to visibly disable the UI and was hoping for some magic options that wouldn't require disabling each control individually.
I have been struggling with how to remove the floating/docking/.... popup that appears when you right click on the cvslistbox toolbar. I have successfully removed it from other controls by overiding OnContextMenu. For cvxlistbox it only overides when right clicking the list area itself. If I right click on the toolbar, where the new/delete button is located, it is not overidden. Instead it calls a different CPane derived class which calls OnShowControlBarMenu.
Any help with removing this popup would be appreciated.
I am writing an ActiveX control that uses a CMFCStatusBar. To do so, I added a CMFCStatusBar to a CFrameWndEx and put the latter into my control. This worked just fine; my status bar appears at the bottom of my control. When I set the style of my Frame to CMFCVisualManagerOffice2003, only the status bar appears. That is the behavior I want. However, when I use a better looking style, such as CMFCVisualManagerOffice2007, I get the status bar on the bottom and a title bar across the top. What do I need to change to use the 2007 visual style but without the title bar?
For reference, this is the code I am calling in my Frame's OnCreate():
Please read the gudelines[^] and reformat your post so the code is within <pre></pre> tags and correctly indented. That way we can read it. Secondly try to add a question, as this entry is meaningless.
Once you get that corrected, you should do some serious cleanup to the create() function. No screen I/O should be performed in that function. Prompt the user for input elsewhere and pass that data to the create() function.
Also, the call to newinside the while() loop is wrong.
Is each new node added to the front of the list or the rear? If the front, no while() loop is necessary. If the rear, the while() loop should simply iterate each node until NULL is reached.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
Yes, it is the same. The parenthesis are here just useless.
But, there's a difference between return; and return 0;: the first one is used in a function that returns nothing (void) and the second in a function that returns something (here, probably an integer).
Yes, exactly the same. The addition of brackets makes no difference.
This however is totally different, and only valid in a "void" function - i.e. one which doesn't return a result.
The difference between them can be illustrated as :-
int DoSomething_1(int val)
// some processing
return (0); // has to return a value as it's an "int" function
void DoSomething_2(int val)
// some processing
return; // must not return a value as it's a "void" function
Days spent at sea are not deducted from one's alloted span - Phoenician proverb
To build a solution, you can simple pass in the path to the solution file and optionally a configuration, such as debug or release. Projects are compiled by using the Project switch, and you can build one project at a time, also optionally specifying the configuration to use.
We have several exes that need access to common dialogs for database administration on common tables. Dialogs need access to a database via ADO/ODBC and user interface. We have in the past recreated the same dialog repeatively. Getting tired of doing that. Would like to create for each dialog an EXE/DLL or something that we can link at runtime in case of changes. A DLL looks like the best way. Any BOOKS or PUBLICATIONS out there to exactly guide us from creating , calling from current EXEs, and distribution? Really need step by step not just a reference document. Would just creating an EXE for each dialog and shell execute would work? Pros / cons.
Last Visit: 18-Jan-20 11:08 Last Update: 18-Jan-20 11:08