From mint-bounce@lists.fishpool.fi Sun Aug 8 18:09:42 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=dTV82yZQE8yuSAVn1UN6lKhBoFV9GnnrsL5Rmcj8c8U=; b=FDfV56zFMIg+GnjbrVUiUrU6TOm/svKmZO1QdA6zvkVsRw4mYkhj0n5edILK5EaBfr v3X2c1Kk51/60v6g9d1t09qNHoi4mLJLSNbXNJvnn+b+CyBLlQNddcLoYLnaA3C+IGxy Et/Yc07+8JgN9/dn4L1PRW9dLHufLpvu+Tblk= 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=WAhwt3dhpes23ABPDtAMZNo/wqluRAZhcfhBh5BpTwLOW2i1SPXI5XPuUY36lxtQJf KWhp0T8/58p26r5T3coVw+QxozxrpzgsnS3SFE+lfxeRbkh5I3fIe4MScBbL+Am24JZs D6O/yrYUC7FyxQk9mM0+bupNLTJO3dp/Jugww= 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: <4C5F1671.1080107@online.no> Date: Mon, 9 Aug 2010 00:08:19 +0200 Cc: mint@lists.fishpool.fi Message-Id: References: <162697.648254351-sendEmail@descaro> <4C59C37A.8090407@online.no> <4C5F1671.1080107@online.no> To: Jo Even Skarstein 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 o78M9flX018419 8 aug 2010 kl. 22.41 skrev Jo Even Skarstein: > On 08/04/2010 09:53 PM, Helmut Karlowski wrote: > >>>>> I guess these are needed for nested submenus (menu from a menu). But >>>>> then the topmost 'parent' should point to - the window, shouldn't it? >>>>> >>> That doesn't help much, as you can't detect which window the menu is >>> attached when a sub-menu is selected. I suggest abusing msg[1]. This >> >> True. So forget this idea and think about the other suggested ways. > > So what happened here? Did you guys agree on a solution? I solved it by cloning the resource tree used for the menu, and identifying the window using the address of the resource tree. -- PeP