AnsweredAssumed Answered

vrf Handling "structure" types returned from compiled functions

Question asked by VRFuser on Apr 13, 2008

Like • Show 0 Likes0
Comment • 3

> Isn't it a case of "the impossible
> we can do at once... miracles take a
> little longer" (or the other way around???)

Yes indeed! Remember: always triple your time estimates

> I am trying to disable close [X]
> on my application window in every
> eventuality so the nugget that it
> is always SC_CLOSE (0xF060) is the
> answer to life, the universe and
> everything.

Awesome! And here Mr. Adams would have us believe it's 0x2A! Happy subclassing and give me a shout if you run into any roadblocks.
-SHAWN-

---
You are currently subscribed to vrf as: ming_meng@agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".

No one else has this question

Outcomes

3 Replies

VRFuser Apr 13, 2008 11:33 AM
Mark Correct
Correct Answer
Hi All

Does anyone know of a workaround for working with compiled functions (dll) that return a structure type? Specifically I am interested in using the GetMenuItemInfo function from user32.dll. This function gives information on items in the system menu on a particular windows title bar, ie things like minimize, resize and close button.

I am trying to find a foolproof way to identify menu item that is the close button. I was working on the basis that the close button would always be the last item in the array of menu items but have found this is not always the case if the user is running add-on utilities that add buttons to the title bar.

As always, thanks in advance.

Best regards

Nick

---
You are currently subscribed to vrf as: ming_meng@agilent.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
Like • Show 0 Likes0
Actions
VRFuser Apr 13, 2008 12:12 PM
Mark Correct
Correct Answer
> Does anyone know of a workaround
> for working with compiled functions
> (dll) that return a structure type?

That's impossible

You're looking for a *pointer* to a structure. I know that's splitting hairs but these distinctions are very important!

> Specifically I am interested in
> using the GetMenuItemInfo function
> from user32.dll.

That's certainly possible, but I think you'd have a much easier time using GetMenuItemID followed by GetMenuItemString instead. Better yet, there's probably an even easier way. If you're looking to disable close or do some kind of pre-process close that's relatively "easy" (compared to GetMenuItemInfo).

But wait! There's more! By mentioning the "title bar", I assume you're talking about the System Menu (accessible with Alt+Space), where Close
(Alt+F4) normally is the last item. Well, the good news is you don't need to find the ID. It's always SC_CLOSE (0xF060).

If you're looking to close an application properly (instead of using KillProcess, which we all know should only be used as a last resort), it gets even easier. Just use SendKeys to send the App object Alt+F4. Or send the app's main window a WM_CLOSE (0x10) message.

Notice I say "send", as in SendMessage instead of PostMessage. This guarantees a synchronous close, so that when SendMessage returns the app is either closed or nearly closed (sometimes cleanup tasks can take some time, but effectively the app has closed. By the time SendMessage returns,
IsWindow(hWnd) will return FALSE).
-SHAWN-

---
You are currently subscribed to vrf as: ming_meng@agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
Like • Show 0 Likes0
Actions
VRFuser Apr 13, 2008 2:46 PM
Mark Correct
Correct Answer
Hi Shawn

Isn't it a case of "the impossible we can do at once... miracles take a little longer" (or the other way around???)

I am trying to disable close [X] on my application window in every eventuality so the nugget that it is always SC_CLOSE (0xF060) is the answer to life, the universe and everything.

Seriously... thanks for your help. Much appreciated as always.

Best regards

Nick

-----Original Message-----
From: Shawn Fessenden [mailto:shawn@vrfarchive.com]
Sent: 13 April 2008 20:12
To: 'Nick Evans'; VRF (E-mail)
Subject: RE: [vrf] Handling "structure" types returned from compiled functions

> Does anyone know of a workaround
> for working with compiled functions
> (dll) that return a structure type?

That's impossible

You're looking for a *pointer* to a structure. I know that's splitting hairs but these distinctions are very important!

> Specifically I am interested in
> using the GetMenuItemInfo function
> from user32.dll.

That's certainly possible, but I think you'd have a much easier time using GetMenuItemID followed by GetMenuItemString instead. Better yet, there's probably an even easier way. If you're looking to disable close or do some kind of pre-process close that's relatively "easy" (compared to GetMenuItemInfo).

But wait! There's more! By mentioning the "title bar", I assume you're talking about the System Menu (accessible with Alt+Space), where Close
(Alt+F4) normally is the last item. Well, the good news is you don't need to find the ID. It's always SC_CLOSE (0xF060).

If you're looking to close an application properly (instead of using KillProcess, which we all know should only be used as a last resort), it gets even easier. Just use SendKeys to send the App object Alt+F4. Or send the app's main window a WM_CLOSE (0x10) message.

Notice I say "send", as in SendMessage instead of PostMessage. This guarantees a synchronous close, so that when SendMessage returns the app is either closed or nearly closed (sometimes cleanup tasks can take some time, but effectively the app has closed. By the time SendMessage returns,
IsWindow(hWnd) will return FALSE).
-SHAWN-

---
You are currently subscribed to vrf as: ming_meng@agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".
Like • Show 0 Likes0
Actions

vrf Handling "structure" types returned from compiled functions

Outcomes

Related Content

Recommended Content