Scientist Studies S01_E24

서명되지 않은 ActiveX 거부감 없이(?) 설치하기

deneb — Fri, 01 Dec 2006 09:47:08 GMT

*code sign 생략하기

http://ttylo.cafe24.com/ttblog/348

빠른 메뉴에 명령 프롬프트 추가하는 방법

deneb — Fri, 24 Nov 2006 08:20:14 GMT

출처 : http://cafe.naver.com/leeparkkwang.cafe (나만의 작은 컴퓨터)

OS : Windows XP

Windows XP에서는 실행창에 cmd를 입력하고 확인을 클릭하거나 보조 프로그램의 명령프롬프트 아이콘을 클릭함으로써 명령 프롬프트를 사용할 수 있습니다. 그러나 기본적으로 C:\Document and Settings\사용자 이름 이 기본 경로로 열립니다. 다른 폴더로 이동해야 하는 경우 cd 명령을 이용해야 합니다. 또한 각각의 경로를 입력하기도 쉬운일이 아니죠 ㅠㅠ

폴더를 우측마우스로 클릭한 후 명령프롬프트 메뉴를 클릭하면 해당 폴더의 경로가 프롬프트에 나타나게 할 수 있습니다.

<해결방법>

1. <시작> -> <실행> 또는 Windows 로고키 + R 클릭 -> regedit 입력 후

2. [레지스트리 편집기] 창이 열리면 왼쪽창에서 아래의 키 값을 순서대로 더블클릭하여 열어줍니다.
HKEY_CLASSES_ROOT -> Directory -> shell

3. shell 키 위에서 마우스 우측버튼 클릭 -> <새로 만들기> -> <키> 클릭 -> 이름을 cmd로 입력

4. 새로 만들어진 cmd 키 값위에서 우측 마우스를 클릭하여 <새로 만들기> -> <키> 클릭 -> 이름을 command로 입력

5. 3번 과정에서 만들어진 cmd 키를 클릭 -> 우측창의 (기본값)을 더블클릭 -> [문자열 편집] 대화상자가 나타나면 값 데이터 난에 명령프롬프트 라고 입력 후 <확인> 클릭

6. 4번 과정에서 만들어진 command 키를 클릭 -> 우측창의 (기본값)을 더블클릭 -> [문자열 편집] 대화상자가 나타나면 값 데이터 난에 cmd.exe \"% 1\" 를 입력. cmd.exe를 입력한 후 한칸을 띤 후 \"% 1\" 을 입력

7. 윈도우 바탕화면을 클릭한 후 F5를 클릭

8. 특정 폴더를 우측마우스로 클릭한 후 명령프롬프트를 클릭하면 명령 프롬프트창이 실행되면서 해당 폴더의 경로가 입력되어 있음을 확인할 수 있습니다.

"Flames" ~ Mark Isham

deneb — Fri, 10 Nov 2006 12:15:38 GMT

from Crash [Original Soundtrack]

메일서버 멀티큐 사용으로 서버 부하량 내리기

deneb — Tue, 30 May 2006 11:28:52 GMT

메일서버 멀티큐 사용으로 서버 부하량 내리기

Nochwas - Duo 505

deneb — Tue, 16 May 2006 05:53:54 GMT

Duo 505
"Nochwas" music promo
from the album "Late"
a video by Lorenzo Fonda and Luca Mathia Bertoncello

Director > Lorenzo Fonda
Production Designer > Luca Mathia Bertoncello
Executive Producer > Joe Togneri
Director of Photography > Giulio Tami
Big puppets Stylist > Rebekka Hirst
Production > Fabrica

Install Oracle 9i on CentOS

deneb — Sat, 06 May 2006 09:15:42 GMT

너무 존경스러워서 울뻔 했다 ;ㅁ;
CentOS 4.2 기준이지만 4.3에서 무난히 적용된다.
자, 그 감동속으로 빠져보자~

Install Oracle 9i on Centos

Drag and Drop, Drag & Drop, 드래그 앤 드롭

deneb — Thu, 13 Apr 2006 08:57:02 GMT

CWnd::DragAcceptFiles
void DragAcceptFiles( BOOL bAccept = TRUE );

Parameters

bAccept Flag that indicates whether dragged files are accepted.

Remarks

Call this member function from within a window, using a CWnd pointer, in your application뭩 CWinApp::InitInstance function to indicate that the window accepts dropped files from the Windows File Manager or Windows Explorer.

Only the window that calls DragAcceptFiles with the bAccept parameter set to TRUE has identified itself as able to process the Windows message WM_DROPFILES. For example, in an MDI application, if the CMDIFrameWnd window pointer is used in the DragAcceptFiles function call, only the CMDIFrameWnd window gets the WM_DROPFILES message. This message is not sent to all open CMDIChildWnd windows. For a CMDIChildWnd window to receive this message, you must call DragAcceptFiles with the CMDIChildWnd window pointer.

To discontinue receiving dragged files, call the member function with bAccept set to FALSE.

======================================================

CWnd::OnDropFiles
afx_msg void OnDropFiles( HDROP hDropInfo );

Parameters

hDropInfo

A pointer to an internal data structure that describes the dropped files. This handle is used by the DragFinish, DragQueryFile, and DragQueryPoint Windows functions to retrieve information about the dropped files.

Remarks

The framework calls this member function when the user releases the left mouse button over a window that has registered itself as the recipient of dropped files.

Typically, a derived class will be designed to support dropped files and it will register itself during window construction.

Note This member function is called by the framework to allow your application to handle a Windows message. The parameters passed to your function reflect the parameters received by the framework when the message was received. If you call the base-class implementation of this function, that implementation will use the parameters originally passed with the message and not the parameters you supply to the function.

======================================================

CWnd::DragAcceptFiles,WM_DROPFILES,::DragAcceptFiles,::DragFinish,::DragQueryFile,::DragQueryPoint

======================================================

IDropTargetHelper
This interface allows drop targets to display a drag image while the image is over the target window.

Remarks
This interface is exposed by the Shell's drag-image manager. It is not implemented by applications.

This interface is used by drop targets to have the drag-image manager display the drag image while the image is over the target window. The IDragSourceHelper and IDropTargetHelper interfaces are exposed by the drag-image manager object to allow the IDropTarget interface to use custom drag images. To use either of these interfaces, you must create an in-process server drag-image manager object by calling CoCreateInstance with a CLSID of CLSID_DragDropHelper. Get interface pointers using standard COM procedures.

Four of the IDropTargetHelper methods correspond to the four IDropTarget methods. When you implement IDropTarget, each of its methods should call the corresponding IDropTargetHelper method to pass the information to the drag-image manager. The fifth IDropTargetHelper method notifies the drag-image manager to show or hide the drag image. This method is used when dragging over a target window in a low color-depth video mode. It allows the target to hide the drag image while it is painting the window.

Note: The drag-and-drop helper object calls IDataObject::SetData to load private formats—used for cross-process support—into the data object. It later retrieves these formats by calling IDataObject::GetData. To support the drag-and-drop helper object, the data object's SetData and GetData implementations must be able to accept and return arbitrary private formats.

For further discussion of Shell drag-and-drop operations, see Transferring Shell Data Using Drag-and-Drop or the Clipboard.

Methods
IDropTargetHelper exposes the following methods in addition to IUnknown.

DragEnter Notifies the drag-image manager that the drop target's IDropTarget::DragEnter method has been called.
DragLeave Notifies the drag-image manager that the drop target's IDropTarget::DragLeave method has been called.
DragOver Notifies the drag-image manager that the drop target's IDropTarget::DragOver method has been called.
Drop Notifies the drag-image manager that the drop target's IDropTarget::Drop method has been called.
Show Notifies the drag-image manager to show or hide the drag image.

See Also
IDragSourceHelper

Requirements
Version 5.00 and later of Shell32.dll

Windows NT/2000: Requires Windows 2000.
Windows 95/98/Me: Requires Windows Me.
Header: Declared in Shlobj.h.

======================================================

IDragSourceHelper
This interface is exposed by the Shell to allow an application to specify the image that will be displayed during a Shell drag-and-drop operation.

Remarks
This interface is exposed by the Shell's drag-image manager. It is not implemented by applications.

Use this interface when you want to specify the image that will be displayed during a Shell drag-and-drop operation. The IDragSourceHelper and IDropTargetHelper interfaces are exposed by the drag-image manager object to allow the IDropTarget interface to use custom drag images. To use either of these interfaces, you must create an in-process server drag-image manager object by calling CoCreateInstance with a CLSID of CLSID_DragDropHelper. Get interface pointers using standard COM procedures.

The IDragSourceHelper interface provides two alternative ways to specify the bitmap to be used as a drag image:

Controls that have a window can register a DI_GETDRAGIMAGE window message for it and initialize the drag-image manager with IDragSourceHelper::InitializeFromWindow. When the DI_GETDRAGIMAGE message is received, the handler puts the drag image bitmap information in the SHDRAGIMAGE structure that is passed as the message's lParam value.
Windowless controls can initialize the drag-image manager with IDragSourceHelper::InitializeFromBitmap. This method allows an application to simply specify the bitmap.
Note: The drag-and-drop helper object calls IDataObject::SetData to load private formats—used for cross-process support—into the data object. It later retrieves these formats by calling IDataObject::GetData. To support the drag-and-drop helper object, the data object's SetData and GetData implementations must be able to accept and return arbitrary private formats.

For further discussion of Shell drag-and-drop operations, see Transferring Shell Data Using Drag-and-Drop or the Clipboard.

Methods
IDragSourceHelper exposes the following methods in addition to IUnknown.

InitializeFromBitmap Initializes the drag-image manager for a windowless control.
InitializeFromWindow Initializes the drag-image manager for a control with a window.

Requirements
Version 5.00 and later of Shell32.dll

Windows NT/2000: Requires Windows 2000.
Windows 95/98/Me: Requires Windows Me.
Header: Declared in Shlobj.h.

VS2005 배포 관련

deneb — Mon, 20 Mar 2006 05:55:24 GMT

http://www.codeproject.com/cpp/vcredists_x86.asp
http://blogs.msdn.com/nikolad/archive/2005/09/02/460368.aspx

OK, due to popular demand, and my frustration with seeing so many people using Express that simply want to run an app on another machine, without the hassle of learning about merge modules, Windows Installer, etc, etc, etc, here is a way to perform deployment option number 2 above (i.e. installing C Runtime library applocal) for Express.

1) On the machine you have Express installed, create the following folder and subfolders in your
program filesmicrosoft visual studio 8VC folder:

redistx86Microsoft.VC80.CRT

2) Copy msvcr80.dll, msvcp80.dll, msvcm80.dll from
windowswinsxsx86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd

into:

program filesmicrosoft visual studio 8VC edistx86Microsoft.VC80.CRT

3) in the above Microsoft.VC80.CRT folder, create a new file named:

Microsoft.VC80.CRT.manifest

4) Paste the following content into the above manifest file:

            type="win32"
        name="Microsoft.VC80.CRT"
        version="8.0.50608.0"
        processorArchitecture="x86"
        publicKeyToken="1fc8b3b9a1e18e3b"
    />

Now you have a new folder in your Visual C++ Express installation that can be re-used when ever you need it.

To deploy these files, simply copy the Microsoft.VC80.CRT folder you just created to your program folder. That's it. So for example, if your application executable resides in C:Program FilesMyApp, you'll have a folder named:

C:Program FilesMyAppMicrosoft.VC80.CRT

that contains the 4 files I mentioned (3 DLLs and one manifest file you created by hand)

No installation of anything else is necessary. Just click on your EXE file, and your app will run. No special installation engines are necessary, just make your setup program (installer) create that subfolder Microsoft.VC80.CRT along with what you normally install with your app)

Let me know if you need similar instructions for MFC and I'll create them.

How To Sort Items in a CListCtrl in Report View

deneb — Wed, 15 Mar 2006 19:16:46 GMT

How To Sort Items in a CListCtrl in Report View

SHGetSpecialFolderLocation 예제

deneb — Wed, 15 Mar 2006 19:14:45 GMT

void WorkWithSpecialFolder() {
// Allocate a pointer to an Item ID list
LPITEMIDLIST pidl;

// Get a pointer to an item ID list that
// represents the path of a special folder
HRESULT hr = SHGetSpecialFolderLocation(NULL, CSIDL_PERSONAL, &pidl);

// Convert the item ID list's binary
// representation into a file system path
char szPath[_MAX_PATH];
BOOL f = SHGetPathFromIDList(pidl, szPath);

// Allocate a pointer to an IMalloc interface
LPMALLOC pMalloc;

// Get the address of our task allocator's IMalloc interface
hr = SHGetMalloc(&pMalloc);

// Free the item ID list allocated by SHGetSpecialFolderLocation
pMalloc->Free(pidl);

// Free our task allocator
pMalloc->Release();

// Work with the special folder's path (contained in szPath)
}