From mint-bounce@lists.fishpool.fi Wed Aug 4 14:18:25 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=40I9W1AgdIRHU7ZYWiYynEGTNLAvSH/xPLEZ1MgoqGA=; b=YT9k+z8xIz6FbkYpJ2vC+Fttzod5gCxS9RztHzyj7Pmh6Gloi2LVFbg0bA3mEGQwte 2BJtINhuP5wdwqj7LCSfRjYifBQzhx9+sQ8hgj3AVnVPfSoupWVsgP4zWlnjUYlm16MT ygx/+O32fy0r/BTOn7dDn6SehySzkTUm0LXqk= 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=cEIewRCmZPZhyVUETI3cmNVrFlpE4SrVwc6+B6yH2jR2lWGtJaHyybkkyHgcCP/dOK UmF8SRteWjzeBJEul2R0eCDeWsMmo3fE+l5ABtNkyEBA4hfBQ0wCxCX7EJQWt18d6Nlz Xa2cpLKBatWFUjvrgtn1xEI05L1DftwmF9NMY= 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: <801809.953848959-sendEmail@descaro> Date: Wed, 4 Aug 2010 20:15:17 +0200 Cc: "mint@lists.fishpool.fi" Message-Id: <9792CD04-599E-4291-A1F7-763480A8B184@gmail.com> References: <801809.953848959-sendEmail@descaro> To: Helmut Karlowski 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 o74IIO2J007978 4 aug 2010 kl. 19.56 skrev Helmut Karlowski: > Maybe this says something to you: > > titles = k->m.titles; > about = k->m.about; > ks = k->p.parent; > kc = k->m.current; > > ks is msg[7], kc msg[3]. I don't know what's what ... I have to test it to be sure. >>> It would not be very easy to make the message longer - it's a generic >>> funtion for all messages, better would be to misuse another parameter = >> - >>> trying to avoid the risk that some other app may get confused. >> >> Some other app shouldn't get confused, because that app shouldn't have = >> received the message in the first place? > > No, but this would be done for every submenu in any app that has one. Ok, then it affects legacy applications too. Better be careful, then. > I really do not think that it's a valuable information for a client to > know who sent an MN_SELECTED (who else could/would do this other than > the AES?) Probably not :) Another solution would be to only allow menu bar access on topped windows. The API problem goes away, and does it really matter for the user? -- PeP