From mint-bounce@lists.fishpool.fi Thu Aug 13 03:20:21 2009 Message-ID: <7A156F8A5E2D4205AC65D78942BA9FCF@joevenlt> From: "Jo Even Skarstein" To: References: In-Reply-To: Subject: Re: [MiNT] qed Date: Thu, 13 Aug 2009 09:18:16 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="ISO-8859-15"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8064.206 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8064.206 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: joska@online.no Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: -------------------------------------------------- From: "Helmut Karlowski" Sent: Wednesday, August 12, 2009 11:02 PM To: Subject: [MiNT] qed > is anybody involved in qed-development, or cf-lib? > > There is a problem with the windowed dialogs and XaAES. > > Select Options -> for files -> edit and press cursor-down or up and see > what I mean. > > I traced this and found that XaAES is doing it right. I see the problem. It's a bit strange, because if you look at the code it looks like CFlib doesn't do any keyboard navigation when running under XaAES. However, it does use it's own "find_edit()"-function in cf_form_do(), and this find_edit() searches for the next/previous editfield by object index and not by coordinates like XaAES does. I don't have the time to study this any further, but if somebody are working on qed and/or CFlib, I think the custom form_do-handler is the right place to look. I think it would be possible to replace this custom code with simple AES-calls under XaAES. Jo Even