Andrew Peace wrote: Personally I'd rather have something that didn't look right on FireFox than something that just refused to work at all. You mean you don't have User Agent Switcher[^] extention? Go and get it. Now! :) David "Stay Kul And Happy" I.A.

I'm curious as to why people keep saying Windows is easy to set up. The proverbial parental unit's parent would not be able to install Windows either. Mention the term driver to one of them and they'll ask why you're talking about golf when you're working on the computer. For myself, I find Linux easier to set up, especially on hardware that's 6 months+ old. At that point, nearly all the drivers you need are built into a current distro, and you're off and running. With Windows, I wind up using another PC to download an ethernet driver. Then I can get online to download my video driver, but the screen's still in some ridiculously low resolution so web surfing is oh so fun. Then I can get everything else normally. Oh, but then I still have to install all my programs, which under Linux I could've done as part of the base install. I'm not saying Linux is the end all be all (that's OS X j/k, sort-of ;-) ), but I do think you need to really compare it without the preset mind of how things "should be" based on using Windows (*cough* white cursor *cough* :-D ). Look at Linux from the point of view of someone who doesn't know Windows computers inside and out, then look at Windows the same way, and I'll bet your opinions might change a bit.

These are all MFC Window objects. It is possible that during the OnInitialUpdate that the true 'window' have not yet been created? You can check with: ::IsWindow(pFrame->m_hWnd) and if that is not true, your windows don't exist yet, so all widnow rectangles will return empty rectangles. You might have to investigate something like RecalcLayout and call it from some other location once the windows exist.

It depends which parts of the shell you want to extend, icon handlers and overlays are fairly simple while context menu extensions are rather more tricky. It all requires a reasonable amount of com and win32api interop and some fairly defensive programming to prevent errors reaching and crashing the shell if they occur. Some things like property sheets really aren't possible in fully managed code though that may change when the 2.0 CLR is released.

For example, the Indigo communications system will allow an application written with Microsoft's .Net tools to share information with a Java application without the need for special code to bridge the two systems. This must be a hoax. MS would never do that!

Windows xp has an option that will preview the file in thumbnail view. You don't need to preview the file in the left pane. But if you want, windows xp still has the pane to let you preview the file or using the above method. A thousand mile of journey, begin with the first step. APO-CEDC Save Children Norway-Cambodia Office

Many thanks!!! Best regards, Dominik _outp(0x64, 0xAD); and __asm mov al, 0xAD __asm out 0x64, al do the same... but what do they do?? ;) (doesn't work on NT)

Provided you don't move the variables around within the baseclass you should maintain ABI (Application Binary Interface), google should be a good starting point for getting information specific for your compiler. As the previous poster pointed out, one one to do this is to use an approach like that of COM, with interfaces for versioning rather than changing implementations. If this is for an in house product it's probably not worth worrying about. Recompile everything to be safe if you're not sure. If you're selling it to other developers look for a more robust way of doing this, COM or XCOM. If you can keep you head when all about you Are losing theirs and blaming it on you; If you can dream - and not make dreams your master; If you can think - and not make thoughts your aim; Yours is the Earth and everything that's in it. Rudyard Kipling

What I normally do when given such a requirement is to "block off" a set of contiguous command IDs within resource.h that accommodate for the maximum number of elements in the dynamic menu. #define ID_DYNAMIC_MENU_START 200 #define ID_DYNAMIC_MENU_RESERVE1 200 #define ID_DYNAMIC_MENU_RESERVE2 201 #define ID_DYNAMIC_MENU_RESERVE3 202 #define ID_DYNAMIC_MENU_RESERVE4 203 #define ID_DYNAMIC_MENU_END 203 Notice I have the DYNAMIC_MENU_START and DYNAMIC_MENU_END pointing at the first and last dynamic menu item respectively. I fill in the ones in the middle as we do not want them used by other resources. We can now set the menu range accordingly. Add to the .h afx_msg void OnDynamicMenu(UINT nID); Add to the message map ON_COMMAND_RANGE(ID_DYNAMIC_MENU_START, ID_DYNAMIC_MENU_END, OnDynamicMenu) Add to the .cpp void CMyClass::OnDynamicMenu(UINT nID) { // nID is the ID of the menu clicked } Ant. I'm hard, yet soft. I'm coloured, yet clear. I'm fruity and sweet. I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain)

Are you using the shell to do some work for you? Because there is no shell when no users are logged on... If you havn't, you should develop your program as a service[^]. Hope this helps.. Multiply it by infinity and take it beyond eternity and you'll still have no idea about what I'm talking about.

John, if you're a diabetic, you really need to check your glucose level. You sound like you're running at a level of 30 or so. :laugh: Software Zen: delete this;