View Single Post
Old 10-09-2013, 08:12 AM   #11
twobob
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr
twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.
 
twobob's Avatar
 
Posts: 6,586
Karma: 6299993
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
The issue with launching matchbox keyboard is that - quite frankly - it is something else to go wrong. To yoke the keyboard like baf does "-xid" would require rewriting the guts of the apps layout.

But possibly, since the keyboard is now being manually invoked, there could ultimately be a version that invokes "your" version of matchbox keyboard for the notes section as you ask.

Once the app is at completion stage perhaps we could look at it?
Have to check but it does sound doable.


EDIT: Actually.. thinking about it... If I externalise all the calls to invoking the keyboard into a script then that would allow the user to twiddle "after the fact".

(In case that doesn't easily translate, Twiddling after the fact means changing the released setup)

yeah... okay... I'll make it a script... on that.

Last edited by twobob; 10-09-2013 at 08:19 AM.
twobob is offline   Reply With Quote