I'm wrong - I thought the JFIF came at the start of a JPEG file - having just looked at a JPG in a hex editor, it doesn't. Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p

That's exactly right. I naively thought it is as that's what I was able to do with Visual Studio Automation and Extensibility methods. I simply looked up the face ID and specified it in a method, say AddCommandBar2() (Commands ojbect, EnvDTE namespace). And the icon I picked would appear accordingly. I initially hoped the FaceID resource is somehow accessible globally. This is embarassing :^) Thanks for the help to clearing this out :-D Reference: FaceID Browser[^]

J.B. wrote: Thanks again Roger, for very informative reply and link. They helped greatly. You're most welcome Johnny. I'm pleased to hear that I was able to help you, so thanks for telling me. :) "It's supposed to be hard, otherwise anybody could do it!" - selfquote "High speed never compensates for wrong direction!" - unknown

Perhaps there's a trick that I'm not aware of, but I don't think you can get the size of the vtable in runtime. If you create an interface that inherits from IUnknown, the first 12 bytes of the vtable will be the addresses of QueryInterface(), AddRef() and Release(). The next four bytes will contain the address of the first method for the new (child) interface and so on until the vtable is complete. The bytes following the vtable will contain data for the member variables, there's no "padding" or "termination" of the vtable, hence I don't think you can tell the size of it in runtime. Perhaps there's a trick when building for 'Debug', but I don't think so. On the other hand: why do you want to know the size of the vtable? :confused: Perhaps there's another solution for your problem. -- Roger "It's supposed to be hard, otherwise anybody could do it!" - selfquote "No one remembers a coward!" - Jan Elfström 1998 "...but everyone remembers an idiot!" - my lawyer 2005 when heard of Jan's saying above

Hi Steve, wow, thanks for the reply. That's the best answer I could've asked for. Thanks again! J.B.

Looks like something generated from one of typelib - if you've process all the Office typelibs, then it's prolly around somewhere (might have a different name though). You must be careful in the forest Broken glass and rusty nails If you're to bring back something for us I have bullets for sale...

J.B. wrote: I did some search and found the possible use of OBDC Excel driver. Am I heading the right direction? Yes. "Ideas are a dime a dozen. People who put them into action are priceless." - Unknown

I think I sort of know now - UpdateWindow(hWnd) only places a WM_PAINT message in the message queue, which leads to an execution of the WM_PAINT's message handler finally. If at that time the client area is all validated already, the window will not be re-painted. On the other hand, InvalidateRect(hWnd, NULL, FALSE) explicitly invalidates the client area and then sends a WM_PAINT message. This makes sure the window will always be re-painted when the WM_PAINT message handler reaches its time. It does two things instead of just one. Please correct me if I am wrong here. Thanks

No, you can't partially specialize a member function. The language allows you only to fully specialize a member function. For instance, the following is valid: // no class specialization prior to this template<> inline void stack<char*,1024>::push(char* const) { } but I'm afraid this is not what you're after, sorry. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo Want a Boost forum in Code Project? Vote here[^]!

vcplusplus wrote: float a = 2.4;warning C4305: 'initializing' : truncation from 'const double' to 'float'float b = 2.4f; It makes a difference. I suppose the appended f tells the compiler to treat the numbers as float type? Thanks.

Thanks Roger, I tried to handle CBS_SELENDOK message and the return string is still an empty string. The handler function looks like below: void CMyDlg::OnCbnSelendokMycombo() { UpdateData(TRUE); CString szMyCombo; m_MyCombo.GetWindowText(szMyCombo); if (v_szMyCombo.IsEmpty()) return; } both szMyCombo and v_szMyCombo return empty strings. v_szMyCombo is the CString value variable for the combo box. Again, if I change the combo box style to "Drop List", the return string is correct. Any other ideas?

The WIN32 API is a bit of a minefield when it comes to BOOL processing. On NT the API might return a true TRUE/FALSE while on Win9x, then API might return ==0/!=0. This is why I always say to play it safe and never test for "== TRUE". Tim Smith I'm going to patent thought. I have yet to see any prior art.

Hi Kuphryn, perhaps my original post wasn't not clear. That's exactly what I was doing in the first place, to add the WM_PAINT handler by overriding OnPaint() in the sub-class. The problem I am having is that OnPaint() is never called if I use the sub-class directly with the control I created from the resource view. But if I explicitly create the control in run-time using Create(), OnPant() gets called no problem. You can look my first post for the example. Thanks.

Thanks Chris, that works for me :-D

Exactly!

Thanks again, Antony, unfortunately, that didn't seem to work. HOWEVER, instead of using CString &, I tried LPCTSTR in conjuction with the member variable, and the following code m_resString += ""; no longer gives memory leak (unlike before or ur suggested CString & declaration here). But if I start assigning values into the CString, it still generates memory leak. I am extremely confused now. Is there a resonable explanation here? Thanks

Thanks alot guys, it all makes sense now :)

thanks alot guys, very helpful

Welcome :) Glad to know it helped you.