beta bugs

Re: Looks good overall. Some beta bugs, though. -- Derek Foster
Posted by Alan Jay Weiner ^Ž , Wed, Oct 09, 2002, 03:17:41		Top	Forum

1) The new launcher buttons at the bottom of the screen are very nice. I was pleased that you were able to make the icons from the actual applications actually look good in such a small space. Setup is reasonably intuitive. I was a bit skeptical about this feature, but I am impressed at how nice you've been able to make it look.

Thanks! I'm pretty pleased with it - I don't know why Sony didn't make the hard buttons on the black section beneath the screen; seems an obvious place to put 'em to me... But since they're inside the clamshell, they're inconvenient for me. The Application Bar really works nicely for 'em!

I think I'd use Fitaly just for that... :)

2) I am still seeing the bug where switching to the Sony keyboard and trying to use it causes both the Sony Keyboard and the Fitaly keyboard respond to taps, resulting in double keystrokes for each letter hit.

This is a tough one... The way Sony implemented that keyboard it is different from the Palm keyboard, and there's no indication that the keyboard has been enabled. (If Fitaly could detect the keyboard enabling it could turn itself off temporarily.) Worse, Sony's keyboard extensions are operating on pen actions before Fitaly gets them, so it's possible for things to happen without Fitaly ever discovering it. I can detect pen-taps in the small keyboard icon (Sony's) to turn the (Sony) keyboard on and off, but it seems to be not quite reliable; sometimes the icon will do its blue highlighting, but then releasing the pen fails to pop up the keyboard; Fitaly would get confused in that case. :(

I'm digging through their keyboard extensions to see what we can reasonably do - if all we can do is the above, that might be enough to live with it... But I'd like a more reliable means to handle it; either to disable its handling of pen taps and allowing us to launch their keyboard when we want it, or to have it notify us that it's popping up.

I'm sure we'll figure something out soon though.

3) (I noticed this in the first beta, but didn't have a chance to alert you before the second beta arrived). When I use "custom left slides" from the new Fitaly, my Palm crashes, and I must do a soft reset to recover. The message that is displayed is "Fatal Alert custom.c, Line: 138, Could not create custom database." This occurs even if I do a soft reset and then load only the Fitaly Virtual beta 2 (and no other hacks).

Jean already answered this one - known bug; fixed soon...

4) When I invoke FVSetup from the application launcher (not from Fitaly itself), it oftentimes overwrites my first app launcher button with an apparently randomly chosen application, forgetting what I had previously set as the target fo my first app launcher button. I then have to set it back to the correct value prior to exiting.

I'm not seeing this one at all... I just installed the beta version (since my current build is newer) and couldn't reproduce it with that version either... Does it happen if you launch from Fitaly itself? how about via McPhling?

An odd thought... when you launch from the Launcher, where on the screen are you tapping - what location is that relative to FVSetup's screen? (i.e., "on top of the A in Action" etc)

If you change the view in the Launcher, so the pen is at a different place, does it still happen? (I'm wondering if I'm reacting to a spurious pen or something; moving the position may change what happens...)

- Al -