A pretty basic question, but one about which
I've been pondering ... on which CPU architecture(s)
is (say) Wondiws XP available?

Russell

Anyone know the secret to controlling the width of an
stand-alone (not a buddy) Up-Down control from a resource
definition? The height seems to be the only thing that changes.
I am using definitions like:

CONTROL "", IDC_MY_CTRL, "msctls_updown32", 0x0, 10, 10, 20, 20

I expected the last 2 values to control the width and
height, respectively, but the "width" value seems to
have no effect. (Tested over 10 to 40 range.)

Curiously, if I make this into a horizontal "Left-Right"
control, the sizes work as expected:

CONTROL "", IDC_MY_CTRL, "msctls_updown32", UDS_HORZ, 10, 10, 24, 12

I'd really like to keep everything in the resource. I know
I could use MoveWindow or SetWindowPos in the main
program (after messing around with dialog-to-pixel conversion).
Likewise, I presume I could do this with CreateUpDownControl and
monitoring UDN_DELTAPOS messages, but that's certainly a
lot messier than a simple resource definition... if only
it worked!

Any ideas? Thanks!

For fn. SHCreateDirectory(hwnd, pszPath, psa), MSDN states that the
max length of pszPath is 248 characters. Is this a mistake? I
noticed that for the fn. SHCreateDirectory(hwnd, pszPath), the str len
is specified to be no more than MAX_PATH charcters or 260 characters.
Puzzled?

The Windows Live Messenger application includes the following option:

[x] Show me as "Busy" and block my alerts when I'm running a
full-screen program or presentation settings are turned on

Does anyone know how to figure out if another app is full-screen?
Does anyone know how to access these "presentation settings"?

Thanks,

Jeff
Gibsons, B.C.
Canada

Hello,

I am developing an Internet Explorer toolbar plugin. A problem is that
opening a new IE tab causes a new instance of the toolbar to be
created. I would like to avoid this since and use a sharing mechanism
instead.

I would like to know the recommended approach for this problem. One
solution that I am thinking of is to have a small windows application
running in the background that manages the application state. Then
each new toolbar instance would connect to it (using some sort of
IPC).

Can anyone comment on this idea or maybe suggest a alternative
approach? All feedback would be greatly appreciated.

Best regards,

Francis