예지와 예지의 겨울옷. 작년에 그린 건데 요맘때 쯤 입었던 것.
순희가 그린 예지
Posted on Oct 28, 2009
Posted on Oct 28, 2009
Posted on Aug 27, 2009
그제 꿈에서 직립보행을 하는 아기 코끼리가 예지랑 노는 꿈을 꿨다.
꿈에서도 어떻게 코끼리가 두 발로 서서 걷는지 좀 신기해했는데
너무 자연스러워서 그냥 아 코끼리는 어렸을 땐 두 발로 걷는구나 하고 다시 딥슬립 했던 것 같다.
예지랑 동물원에 자주 가고 어린이 비디오를 너무 본 탓일까?
갑자기 꿈을 꿨던 게 기억이 나서 적어본다.
Posted on Jun 17, 2009
You may see the following error message when you compile DirectShow with the latest version of DirectX SDK. (the current version is “DirectX SDK – March 2009” at this moment)
C:\Program Files\Microsoft SDKs\Windows\v6.0A\include\qedit.h(498) : fatal error C1083: Cannot open include file: ‘dxtrans.h’: No such file or directory
This is because “dxtrans.h” is not included in the latest version of DirectX SDK any more (from DirectX SDK – November 2007) although “qedit.h” of DirectShow is still dependent on it.
I found an article posted by people who were already troubled with this problem. The point is that the part of “qedit.h” which depends on “dxtrans.h” is not necessary to use DirectShow, so you comment it out in “qedit.h” and the error will be gone. (For the details, see this) The other solution which I like better is to define some keywords before including “qedit.h” to prevent the “dxtrans.h” dependent code from being compiled. Then, you don’t need to edit “qedit.h” itself.
#pragma include_alias( "dxtrans.h", "qedit.h" ) #define __IDxtCompositor_INTERFACE_DEFINED__ #define __IDxtAlphaSetter_INTERFACE_DEFINED__ #define __IDxtJpeg_INTERFACE_DEFINED__ #define __IDxtKey_INTERFACE_DEFINED__ #include <qedit.h>
FYI. DirectShow is not a part of DirectX SDK any more, and is moved to Microsoft Windows SDK (which has been called Platform SDK for a while). Windows SDK is installed as a part of Visual Studio 2008, so you don’t need to install it additionally to use DirectShow unless you want the latest version of Windows SDK.
Posted on May 31, 2009
I’ve had to deal with a pointer of a BSTR string returned to an event handler of an ActiveX control. I wanted to convert it to LPCTSTR, and a simple implicit type-casting worked seamlessly when I tried in a test project.
void put_UseServer(LPCTSTR newValue); void ServerChanged(BSTR* NewServer) { put_UseServer(*NewServer); // This conversion works only in Unicode Character Set }
However, when I copied the same code into my actual project, it caused an error. The reason was that my project used the Multi-byte Character Set whereas I tested the code in the Unicode Character Set. The simplest solution I found which also works in the Multi-byte Character set is like the following.
void put_UseServer(LPCTSTR newValue); void ServerChanged(BSTR* NewServer) { put_UseServer(COLE2CT(*NewServer)); // Use ATL String Conversion Class }
More information about ATL and MFC String Conversion is on the MSDN website.
Posted on May 30, 2009
I experienced this trouble when I tried to add a variable with a wizard in Visual Studio 2008. I never suspected IE8, but MS disappointed me again. Anyway, here is a workaround posted in Visual C++ Team Blog and it seems to work. For the details, click HERE
Please follow the following steps:
– Open regedit (on a 64-bit OS, open the 32-bit regedit)
– Under “HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones“, create a new key called 1000 (if it isn’t already there)
– Under 1000, create a DWORD entry with:
o Name = 1207
o Type = REG_DWORD
o Data = 0x000000
For the workaround to work on VS2005, however, the VS2005 SP1 (and VS2005 SP1 Update for Windows Vista) has to be installed.