handle

问题 Here is the code from switch in WndProc function I've been given as an example: case WM_PAINT: hdc = BeginPaint(hWnd, &ps); // Create a system memory device context. bmHDC = CreateCompatibleDC(hdc); // Hook up the bitmap to the bmHDC. oldBM = (HBITMAP)SelectObject(bmHDC, ghBitMap); // Now copy the pixels from the bitmap bmHDC has selected // to the pixels from the client area hdc has selected. BitBlt( hdc, // Destination DC. 0, // 'left' coordinate of destination rectangle. 0, // 'top'

问题 I am trying to create a subplot (6 plots) of world maps into which I am writing chosen shapefiles. My issue is with my placement of subplots: They are overwriting each other. I understand from the other questions like this on stackoverflow, that it is because the axes are overlapping somehow. But I thought I had created positions that they would just be 'side-by-side' (see code below). I have tried to make the axes transparent and that doesn't seem to help. My question is: how can I modify

问题 My scenario Compiled angular projects are saved like . ├── branch1 │ ├── commitC │ │ ├── app1 │ │ │ ├── index.html │ │ │ └── stylesheet.css │ └── commitD │ ├── app1 │ │ ├── index.html │ │ └── stylesheet.css │ └── app2 │ ├── index.html │ └── stylesheet.css ├── branch2 │ ├── commitE │ ├── app1 │ │ ├── index.html │ │ └── stylesheet.css │ └── app2 │ ├── index.html │ └── stylesheet.css └── master ├── commitA │ ├── app1 │ │ ├── index.html │ │ └── stylesheet.css └── commitB ├── app1 ├── index.html └

问题 I have this code: private static void Start(String path) { var process = Process.Start(new ProcessStartInfo(path) { WindowStyle = ProcessWindowStyle.Maximized, UseShellExecute = true, }); ThreadPool.QueueUserWorkItem(Tick, process); } private static void Tick(Object obj) { var process = (Process) obj; while (true) { Debug.WriteLine($"HWND: {process.MainWindowHandle}"); Thread.Sleep(TimeSpan.FromMilliseconds(10)); } } This starts a process and then displays the MainWindowHandle property every

问题 I'm trying to make an application that reads the memory of another (non-Java & 32bit) application using JNA. So far I know how to find process ID and base address of modules. And right before reading memory I need to open process and the OpenProcess function simply returns null. Also, I'm using Windows 10. // process id (pid) is known final int PROCESS_VM_READ=0x0010; final int PROCESS_QUERY_INFORMATION=0x0400; WinNT.HANDLE processHandle = Kernel32.INSTANCE.OpenProcess(PROCESS_VM_READ |

问题 While browsing some code I found a call to OpenPrinter(). The code compiles and works fine. But, we are passing a HANDLE instead of LPHANDLE (as specified in MSDN). I found out that in windef.h the following declaration exists: typedef HANDLE FAR *LPHANDLE; What does LP stand for? Should I use a LPHANDLE , or keep HANDLE ? 回答1: LP stands for Long Pointer. It's a pointer to a handle in this case. HANDLE h = <winapi function>(); LPHANDLE ph = &h; You can use it the same way you would a handle

问题 I am trying to use ShellExecute to open a file in Excel. I was reading about the function on MSDN forums, and I found the folowing information about the handle, which is the first parameter: "hwnd [in] A handle to the owner window used for displaying a user interface (UI) or error messages. This value can be NULL if the operation is not associated with a window." I have also heard this referred to as the handle to the parent window. What is the parent/owner window? As you see below I am using

问题 In the past, I've suffered from a freezing issue that was the result of a Control being used to marshall calls on the UI thread before a handle has been created for that control. (See Kim Greenlee's blog for more info). Using this method - implemented recursively - I ensure all controls that are created in our application have handles when they are constructed. Specifically, this is done after the designer call to initialise the GUI for the control. My question is: Q - Aside from performance,

问题 In the past, I've suffered from a freezing issue that was the result of a Control being used to marshall calls on the UI thread before a handle has been created for that control. (See Kim Greenlee's blog for more info). Using this method - implemented recursively - I ensure all controls that are created in our application have handles when they are constructed. Specifically, this is done after the designer call to initialise the GUI for the control. My question is: Q - Aside from performance,

问题 How does a handle differ from a pointer to an object and also why can't we have a reference to a reference? 回答1: A handle is usually an opaque reference to an object. The type of the handle is unrelated to the element referenced. Consider for example a file descriptor returned by open() system call. The type is int but it represents an entry in the open files table. The actual data stored in the table is unrelated to the int that was returned by open() freeing the implementation from having