From mint-bounce@lists.fishpool.fi  Wed Aug  4 12:53:58 2010
Message-ID: <710474.474446045-sendEmail@descaro>
From: "Helmut Karlowski" <helmut.karlowski@ish.de>
To: "mint@lists.fishpool.fi" <mint@lists.fishpool.fi>
Cc: "helmut.karlowski@ish.de" <helmut.karlowski@ish.de>
Subject: [MiNT] XaAES: menus in windows - window handle?
Date: Wed, 4 Aug 2010 16:51:09 +0000
X-Mailer: sendEmail-1.55
MIME-Version: 1.0
Content-Type: multipart/related; boundary="----MIME delimiter for sendEmail-993781.182755814"
X-Antivirus: avast! (VPS 100804-0, 04.08.2010), Outbound message
X-Antivirus-Status: Clean
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: helmut.karlowski@ish.de
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>

This is a multi-part message in MIME format. To properly display this message you need a MIME-Version 1.0 compliant Email program.

------MIME delimiter for sendEmail-993781.182755814
Content-Type: text/plain;
  charset="iso-8859-1"
  Content-Transfer-Encoding: quoted-printable

Peter Persson wrote:

> Another question related to menu bars in windows,
>
> Is there any way to find out the window handle associated with a menu =
> event? In my project, multiple windows share the same resource tree for =
> the menu, but the menu actions should only operate on a particular =
> window. The event message doesn't tell which window handle it was, and I =
> can't assume it's the top window because it's possible to access window =
> menu bars in the background as well.
>
> The only cure I can come up with would be to generate a separate menu =
> resource tree for each window, and somehow that feels like a bloody =
> mess.
>
> Any ideas?

The only possibility I know is currently to use different trees (just copy
them). Not very nice but should work.

If no one has a better solution it could be added in a future version to
also pass the window-handle. There is still room for additional parameters I
guess.

What does the last parameter ('parent') contain?


Is there a possibility in the bugtracker to add feature-requests?


-Helmut



------MIME delimiter for sendEmail-993781.182755814--


