AFAIK SHGetShortcutTarget is for WinCE only. I assume you're not using WinCE cos you'd probably have said so... Frankly, i'd use the CShellLink class available on this site. You'll also note that links like those which link to microsoft office are in fact special kinds of links which the API can't decode. and they're not documented. It's annoying. Sorry to dissapoint you all with my lack of a witty or poignant signature.

http://msdn.microsoft.com/downloads/default.asp?URL=/code/sample.asp?url=/msdn-files/027/001/566/msdncompositedoc.xml Download the WMI sdk, its full of samples. You will need to do some reasearch on your own and learn about WMI and how it works. Try using the search engine on this site, codeguru and others. Learning to research a problem will server you well in the future. Thanks for the help, Bill

Hi Tomasz, I just got a solution to the problem with a little help from another Codeproject dude [thx Joel!]. The thing is that whenever a WM_ERASEBKGND is received by a CTabCtrl, all window children of CTabCtrl that are CListCtrls don't get properly repainted if they have been "focused". The fix is just to call RedrawWindow on the CListCtrl when ever appropriate. As always Tomasz, thx for your superb help and 'be there'-frequency! /Tommy

Well, I appreciate your help, but the result is not real size... For instance, GetDeviceCaps(LOGPIXELSX/Y) returns a value that is fixed and doesn't depend on any physical settings made on the monitor or even changes made in resolution and physical monitor size. If it would, then everything would have been fine. Try for your self and measure your screen. /T

Of course, but are you telling me you have found something there?!

If you release the bar tracker then it's supposed to splitt at that exact location, not 2 pixels off... don't you agree...? Hmmmm... I would say that most users can't move mouse with pixel or even 2-pixel accuracy. However, I can see that this issue is really important for you ;) Assuming that you have three-way splitter without scrollbar sharing, you could simply implement resizing 'manually' - create the views inside a frame window, leave some space between them, set the frame class cursor to <-|-> (rotated 90 degrees) and handle mouse messages in the frame window. Enter tracking mode at WM_LBUTTONDOWN, capture the mouse, move your views in WM_MOUSEMOVE, end the sequence with WM_LBUTTONUP. This gives you on-the-fly resizing. You may find this technique may be easier to implement than fixing CSplitterWnd. Tomasz Sowinski -- http://www.shooltz.com

On Win2000 you can use UpdateLayeredWindow to create translucent windows. With earlier versions your only solution is to copy background bits to DIB section and compose the foreground bits using some blending function, then copy DIB section to screen as button image. If all you need is completely blue button with icon, handle WM_CTLCOLORBTN. Tomasz Sowinski -- http://www.shooltz.com

Hi again, What must I include in order to use the _APS_NEXT_CON... value?

WM_COMMAND will recieve a BN_CLICKED message which includes the ID of the button and so on. I've been doing it in Win32, but I'm sure you can override WM_COMMAND in MFC, or otherwise do it through PreTranslateMessage otherwise ( the last resort ;0) Christian As I learn the innermost secrets of the around me, they reward me in many ways to keep quiet. Men with pierced ears are better prepared for marriage. They've experienced pain and bought Jewellery.

Ok, good! (or bad) :) Do you know how to fix it? Cause it's definitely a CSplitterWnd bug where they've somehow missed calculating the width of the splitter borders when using nested splitters... /Tommy

If you're unable to find sufficient docs online, check out the book MFC Internals which covers CSplitterWnd and just about everything else in MFC in great detail. --Mike-- http://home.inreach.com/mdunn/ A recent survey reports that 1/4 of all internet users in England surf for porn. The other 3/4 just didn't want to admit it.

In OnInitialUpdate. RECT rc = { 10, 10, 100, 100 }; m\_Button.Create("Caption", WS\_VISIBLE | WS\_CHILD, rc, this, 1); m\_Button.ShowWindow(SW\_SHOW); The 1 is the ID, I suggest creating an ID range in resource.h and using it for dynamically created buttons, then use OnCommand to capture their being pressed. Michael Dunn gave some good advice on how this works in the thread on WTL dynamic buttons I started. Christian #include "std_disclaimer.h" The careful application of terror is also a form of communication. Eagles may soar, but weasels don't get sucked into jet engines.

I tried to do something similar and wasn't sure if it was possible. My workaround was to make the first column in the splitter another CFrameWnd and then split that one to two rows. Bret Faller Odyssey Computing, Inc.

How do you mean...? After I release the mouse button, call setcolumninfo with 2 pixels in the opposite direction... that's ugly!

You'll have to handle WM_NCPAINT. DrawFrameControl can help in button drawing. This was discussed once in MSJ, search your VC++ help for ShadeCap. Tomasz Sowinski -- http://www.shooltz.com