|
I have an application where the user opens many files at once ( MFC MDI ), and the filenames are stored in the MRU list under the File menu. That is fine with me. I would like to disable all these filenames showing up under "Recent Documents" in Windows XP. Is there a way to open files in Win32 and MFC so that the documents do not show up in this list ?
|
|
|
|
|
Are you not wanting files added to the MRU list itself (a CRecentFileList object maintained by CWinAPP), or are you just not wanting the items from the MRU list showing up in the File menu?
Read Paul DiLascia's August 1999 MSDN article about this very subject.
http://www.microsoft.com/msj/0899/c/c0899.aspx
|
|
|
|
|
Checking the MSDN
void LoadStdProfileSettings( UINT nMaxMRU = AFX_MRU_COUNT );
states
Call this member function from within the InitInstance member function to enable and load the list of most recently used (MRU) files and last preview state. If nMaxMRU is 0, no MRU list will be maintained.
If I have seen further it is by standing on the shoulders of Giants. - Isaac Newton 1676
|
|
|
|
|
Sorry, maybe I'm not being clear.
When you click on the start button in Windows XP, a small window pops up and one of the selections is "My Recent Documents". I do not want my files to be added to THAT list.
|
|
|
|
|
Hi,
I'm having a problem with a combobox using VC++ 6 and Windows 98.
When I click in the combobox and call his ondropdown event, it seems that the mouse focus stays in this object and if I click (using mouse) in another control of the dialog, my code calls again the ondropdown event of this combobox.
So, I'm not able to click using mouse in another part of the dialog.
Some tests I have made show that this behaviour occurs just on Windows 98 SO.
Could anybody help me out, please?
Thanks in advance,
Felipe
|
|
|
|
|
I has found a article in the Knowledge Base Q326254.
The important point is
... When the ComboBox control is dropped down, the ComboBox captures the mouse to use its input to select the items that are in the ComboBox. ...
It means, only the ComboBox receives mouse messages while they is dropped down.
 MatLin
|
|
|
|
|
Hi all,
I wish to create a dialog from within my non-mfc dll. I want to start the dialog as soon as possible! Can I do it in PROCESS_ATTACH...? The docs says only simple initialization is allowed there.
Anyone?
/T
|
|
|
|
|
In DLL_PROCESS_ATTACH, I call a function that creates and displays the window. Don't know if this is the correct way, however it works like a charm.
regards
modified 12-Sep-18 21:01pm.
|
|
|
|
|
Can you not have the dialog as a static instance of the dll? Then the dialog will be constructed as soon as the dll is loaded, and its done in the correct order?
|
|
|
|
|
Another way is to define a function Initialise, and when the app loads the dll, call GetProcAddress(yourdllhandle, "Initialise"), which returns a pointer to the function which you can use to start the dialog, whether its modal or not.
|
|
|
|
|
Read the docs on DllMain(), it has lots of warnings about what you aren't supposed to do, such as call APIs outside of kernel32. If your code works, then you're lucky.
--Mike--
Ericahist | Homepage | RightClick-Encrypt | 1ClickPicGrabber
Latest art~!@#2rDFA#@(#*%$Rfa39f3fqwf--=
NO CARRIER
|
|
|
|
|
Oh, I must have overread it, thanks for the info. Maybe I should redesign my code 
modified 12-Sep-18 21:01pm.
|
|
|
|
|
|
Ok... so HOW then do I create and call a dialog/window in a dll as soon as possible...?
Actually, what I want is a splash screen that kicks in when somebody calls LoadLibrary(mydll).
/Tommy
|
|
|
|
|
Inside PROCESS_ATTACH, is this a bad thing to do you mean:
----
hSplash = CreateWindow(
"BUTTON",
"Tommy testing Splash Screen...",
WS_POPUP | BS_FLAT,
(sx-W)/2, (sy-H)/2,
W, H,
NULL,
NULL,
hdll,
NULL);
ShowWindow(hSplash, SW_SHOW);
UpdateWindow( hSplash);
}
// ... processing ...
if ( hSplash)
DestroyWindow( hSplash);
----
|
|
|
|
|
I have not yet resolved my problem ... can anyone help me ?
read this
read this topic
|
|
|
|
|
from :|http://www.codeproject.com/listctrl/changerowheight.asp
Problem:
I don't receive a WM_SETFONT or WM_MEASUREITEM message.
(Damian Williams, 1999-10-18)
Solution:
Modify the style of the list control to "owner draw fixed" (LVS_OWNERDRAWFIXED).
Overload CListCtrlEx::DrawItem().
A WM_MEASUREITEM message will be sent to a parent window of list control.
(Chung Hyun, Lee, 2000-05-25)
Solution 2:
Class Wizard does not show you the =WM_MEASUREITEM reflected message. If you use Class Wizard to get WM_MEASUREITEMS, it can only be handled by a class other than the list view control, i.e. a parent window. This is not satisfactory. To get a reflected message you must add the following in the message map in your .CPP file:
ON_WM_MEASUREITEM_REFLECT()
|
|
|
|
|
Hi,
I need a help once again. What are the proper Window API to check how much of memory space you have allocated and how much virtual memory space you have left ?
|
|
|
|
|
Try
VOID GlobalMemoryStatus(
LPMEMORYSTATUS lpBuffer
);
hth
-ar
|
|
|
|
|
Thanks, does this check for Virtual Memory used by per apps? Or as a system?
|
|
|
|
|
Take a look at GetProcessWorkingSetSize () and see if that's what you need. There's a whole slough of memory management functions in the API, just check out the documentation in MSDN!
-ar
|
|
|
|
|
Hello all,
First post here. I have been reading the site for about one and a half months, great place to be, thanks to all.
Here is my deal: I am programming an MFC App to demo what my company can do. We design avionics software for aircraft simulators, so I am pretty familiar with GDI+ (that is mainly what we use for a couple of reasons, instead of DirectX or OpenGL. You'd be surprised how many real instruments on real planes run on GDI or GDI+).
My idea for the demo is a dialogue that starts off black, our name fades in, then the user is taken to a menu page, where he will have three or four options to click on to see different avionics working. Except I don't want the Windows look at all. The click areas, for example, I want to be designed with GDI+, so that they don't look like buttons, but like the real avionics screens.
Then once he chooses an option by clicking it, the entire dialogue window will become that avionics screen, and it will run through a short loop, basically using my already existing GDI+ code for that instrument, and just using timers to change the variables every 10 ms or so to change things smoothly, like the airspeed bar increasing, the horizon tilting, etc.
I would also like the user to be able to quit the application whenever. I have the intro running right now, being drawn on the OnPaint, but I have to wait for it to finish drawing before I can quit the app.
I am willing to post the fundamental structure (can't post our proprietary code for the instruments, of course) here after this is done to serve as another example of how not to stick to Windows-looking apps.
Any help with any area would be appreciated. Thanks in advance.
Best Regards
Fabio Miguez
|
|
|
|
|
Well, I'm not sure how advanced your demo app is but here's a good way to start. You need to create WM_POPUP window, and so I believe in MFC you have to override the Create() function and specify the flag in the .style property of the CREATESTRUCT variable. This will get rid of the "Windows Look". Then you can draw your own window frame with GDI+ and define its behaviour. Also, you could use MFC buttons and just override the WM_DRAWITEM message (I think, its the Owner drawn stuff anyway) after flagging the button as owner draw in the resource editor. You can assign it as a new class in the wizard that derives of CButton so you can use your customised draw routines for the button. Can't really help you any further til I know I'm on the right lines or not.
Hope this helps,
Alan.
P.S. Why do aircraft instruments use GDI/GDI+ and not DirectX or OpenGL, surely it can't be a reliability issue? Or is it just cos render speed doesn't have to be optimised? I always thought they'd use a monster API to do it, especially since they use CATIA to design the aircraft.
|
|
|
|
|
Hey Alan,
Thanks for the response. You are on the right track. When checking my code, I do not have a Create() function. By pressing Ctrl+W I can check in the MFC Wizard that I can add that function to the code, but I am not sure what to do with it.
I had thought about the owner drawn for the buttons, although I have not experimented with it. But as far as I understand, by doing that, I will be able to assign a region for the button, and later assign a function to that hit, all I have to do is make sure I draw my button exactly where that area is defined, right?
I am not sure why GDI/GDI+ is used. But that is a generalization. Some avionics use OpenGL, and some use proprietary APIs, since they are not even running Windows. But I believe the advantage of GDI/GDI+ is the ready-to-use drawing functions. And the refresh rate on some avionics, like moving maps, is very small, like 1 frame per second. As I understand, DirectX does not come ready with drawing functions, but I could be wrong.
Thank you for the help so far. Let me try and play with owner drawn buttons to see what happens.
Best Regards
Fabio Miguez
|
|
|
|
|
There is a bug in Visual Studio 2003 which prevents you adding ATL OLEDB consumers to MFC projects. This previously worked in Visual Studio 2002.
The work around is to fool the ATL wizard into thinking it's not an MFC project
Change your CWinApp inherited class as follows
#ifdef _FAKED
class CG1App : public CObject
#else
class CG1App : public CWinApp
#endif
The wizard now works and the project compiles correctly.
NB. you will still need to add the required header
atldbcli.h
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
