From mint-bounce@lists.fishpool.fi Fri Sep 7 21:14:25 2007 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de From: "Jo Even Skarstein" To: "MiNT email list" Subject: [MiNT] SV: SV: SV: form_button in XaAES Date: Fri, 7 Sep 2007 21:07:18 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 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: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=0.6 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00, NEW_DOMAIN_EXTENSIONS X-Spam-Level: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by wh58-508.st.uni-magdeburg.de id l87JEOHL019906 > -----Opprinnelig melding----- > Fra: mint-bounce@lists.fishpool.fi > [mailto:mint-bounce@lists.fishpool.fi]På vegne av Jo Even Skarstein > > Don't let the AES handle keyboard events unconditionally, let the > application pass it back to the AES after it has done what it > needs with the > event. > > Let's say we offload everything that has to do with editable text > fields to > the toolbar handler, but that it needs to be passed keyboard > events from the > application. We could introduce a new call (or an extension to an > existing) > for this: There's also a different way of doing this. As most dialogs are just that - dialogs, there would rarely be a need for a specific user area. Such dialogs would benefit greatly from having the AES handle these completely like Olivier does in MyAES. Then we have the cases where a toolbar really is a toolbar - e.g. in a text editor window. Having the application handle keypresses the old fashioned way (form_keybd) would be acceptable. So by adding another mode to wind_set(TOOLBAR) could solve this problem - one mode where the AES handles both mouse button events as well as keyboard events, and one mode where toolbars behaves like today. Jo Even