From mint-bounce@lists.fishpool.fi Sun Aug 8 18:48:32 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=oDc7ty7X9Ls13ui2RjP8zBX8VJ/SMQo92CCF6BQ5beg=; b=L7tXudP77mJBA02iFOKP5kA9C9uz6fOAmaZUJoKcBDYBOqqJZQN9YP9Gm5qQO/bQBL Im60FuRQ9lZl5w7poypx78TkkroV2G1jaAusI4e3Qe5n0N1mFbzYPGf39jJ//gsaRZ1N 9/2OZyjwu2GL5fMX/ENKZFvFJmoQd0SejdVTY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=rKxXBgwc5O0rKp4fFkj2AhOa5w9o6/t5DRGAb+kyOs3+JiA4v2qLjygItnaqLdMy9q qypfIXkJLWSEAkR2gABCtVqiDtGgtHS+l77rchX+1/W7T8M5UqgnkueCn0CVRtXWa9Zi C5oJkQWeBQCM2fpc0LM8vyzHCIkTujlFlNTag= Subject: Re: [MiNT] XaAES: menus in windows - window handle? Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Peter Persson In-Reply-To: <4C5F2E60.8020509@chello.nl> Date: Mon, 9 Aug 2010 00:46:56 +0200 Cc: mint@lists.fishpool.fi Message-Id: <0EB389F9-5D48-4F08-B7C2-3F6578EF247B@gmail.com> References: <162697.648254351-sendEmail@descaro> <4C59C37A.8090407@online.no> <4C5F1671.1080107@online.no> <4C5F2E60.8020509@chello.nl> To: Henk Robbers X-Mailer: Apple Mail (2.1081) X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: pep.fishmoose@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o78MmVqR032270 9 aug 2010 kl. 00.23 skrev Henk Robbers: > Peter, you must be a very nice and cooperative guy. > I sincerely hope you will never get regrets about such a hack. I beg your pardon??? MN_SELECTED returns the address of the object tree associated with the menu event. It's been that way since 1985, and right now that's the only way to uniquely identify an event as belonging to a particular menu. There is no other way to do that. All I do is to tag each window with the address of its menu bar, and evaluate this information each time I receive a MN_SELECTED event. In my case, I needed to clone the menu resource anyway, since the contents of the menu depends on the contents of the window. If you know of a less ugly solution, please feel free to spill the beans. -- PeP