Clik here to view.
re: Why does ShellExecute return SE_ERR_ACCESSDENIED for nearly everything?
@Joshua: If this blog teaches anything, it's that you just know that somewhere out there is an application which actually relies on those being two different responses.
View ArticleClik here to view.
re: Why does ShellExecute return SE_ERR_ACCESSDENIED for nearly everything?
@AndyCadley: I somehow can't help but imagine a whole cadre of Microsoft software developers, paralyzed with fear at their terminals, who *want* to write software but know that every decision they make...
View ArticleClik here to view.
re: The cries of "Oh no!" emerge from each office as the realization slowly...
@Kevin: Actually this new variant is to play with students that happens to have Unix cluster account (usually without root access), so "rm -rf /" would have no effect anyway even without that...
View ArticleClik here to view.
re: If there's a problem with a wiki, then you can fix it; that's why it's a...
One problem with a wiki for team docs is that "everybody is responsible for keeping this up to date" is surprisingly similar in effect to "nobody is responsible for keeping this up to date"
View ArticleClik here to view.
re: Why does ShellExecute return SE_ERR_ACCESSDENIED for nearly everything?
> ... who *want* to write software but know that every decision they make irrevocably binds them. That's how it is in programming, we just have to get used to it. Â You start with an infinite...
View ArticleClik here to view.
re: If there's a problem with a wiki, then you can fix it; that's why it's a...
@Douglas: Apparently (to me, anyway) your company doesn't understand the wiki model. It should be editable by everyone in the organization who has access to see it in the first place. "But someone...
View ArticleClik here to view.
re: Using WM_COPYDATA to marshal message parameters since the window manager...
The size of WINDOWPOS would be incorrect if one process was 32-bit and the other was 64-bit. Â I would this this by sending a different structure that only contained the x, y, cx, cy and flags fields....
View ArticleClik here to view.
re: Using WM_COPYDATA to marshal message parameters since the window manager...
You can of course send a WM_COPYDATA back to the "client" if you need to return data but if you need to send a lot of these messages it might be better to use SHAllocShared or some other shared memory...
View ArticleClik here to view.
re: Using WM_COPYDATA to marshal message parameters since the window manager...
"No deadlock here, because a thread can process inbound sent messages while waiting for an outgoing sent message to complete. -Raymond" I don't get it. Â If both threads/processes are using SendMessage...
View ArticleClik here to view.
re: Why does ShellExecute return SE_ERR_ACCESSDENIED for nearly everything?
@mikeb: You mean "if the handle is less than *or equal to* 32", right? It's the little things that get you.
View ArticleClik here to view.
re: Using WM_COPYDATA to marshal message parameters since the window manager...
Well that's a lot cleaner than XxxxProcessmemory. And it handles 32/64 bit correctly if your structs are defined sanely* (system structs often aren't). *local definition is suitable for use in binary...
View ArticleClik here to view.
re: Using WM_COPYDATA to marshal message parameters since the window manager...
@JamesJohnston blogs.msdn.com/.../150929.aspx
View ArticleClik here to view.
re: Using WM_COPYDATA to marshal message parameters since the window manager...
WM_COPYDATA is also fast. I was writing a logger process and was surprised that it would log thousands of log string per second -- each send with WM_COPYDATA from another process. Impressive!
View ArticleClik here to view.
re: Using WM_COPYDATA to marshal message parameters since the window manager...
@AsmGuru62: Yeah, copying a contiguous block of data from one memory location to another is very fast, especially if you know what CPU you're using and you can use that to tune the code to use the SIMD...
View ArticleClik here to view.
re: If there's a problem with a wiki, then you can fix it; that's why it's a...
@Brian EE I'm with you all the way. Unfortunately, there's nothing I can do to change it.
View ArticleClik here to view.
re: Using WM_COPYDATA to marshal message parameters since the window manager...
Does anybody know when WM_COPYDATA was created? Obviously it had to exist for Win32 to work (because different windows could have different address spaces), but it's not clear that there was a use for...
View ArticleClik here to view.
re: If there's a problem with a wiki, then you can fix it; that's why it's a...
> your company doesn't understand the wiki model. Wiki is not just a technology, its also a religion.
View ArticleClik here to view.
re: Using WM_COPYDATA to marshal message parameters since the window manager...
@Gabe: I remember noticing it in the pre-release docs for Win32 and I remember thinking it was new. As you say, Win16 doesn't need it and Win32 almost certainly does.
View ArticleClik here to view.
re: Using WM_COPYDATA to marshal message parameters since the window manager...
@Gabe: Of course, there's nothing to stop you from sending a 0x004A message in 16-bit Windows and passing an hWnd in wParam and a COPYDATASTRUCT in lParam ;-)
View ArticleClik here to view.