just a thought...since bringing up the menu via touch actually contains the full screen option, and since it is still (a little) hard to tap to bring up the menu...
might it make better sense to do away with the fs button, replacing it with a menu button?
That way you have 2 methods to get to the menu (which contains the full screen option anyway) and the sm (show menu or whatever it would be called) would provide an option that would never require a stylus or perfectly still finger tap.
anyways hope I am not just being a pain cause the app is pretty good as it stands now. It just seems accessing the menu from the polsition the fs button is in now would make for better use of the space...opens up more options but still include full screen function...
Robin, could you coordinate with danny.milo@gmail.com.nospam (minus the nospam)? He's got a version based on 0.14 which doesn't crash. See his website for his changes and debs for both n800 and n900.
I've already looked at the code and backported the useful changes. I'll recheck other versions on the N800 and see whether I can reproduce/track down the lock-up issue. I'm also planning on pulling together some patchsets against the current FBReader source code and get them pushed upstream.
Version 0.12.10-15 has just been uploaded with rotation support for the popup menu. I've uploaded both the N800 and N900 version - the N800 still locks up sometimes on loading a book, but the previous version I uploaded suffers the same issue, so I've uploaded the improved version anyway.
just a thought...since bringing up the menu via touch actually contains the full screen option, and since it is still (a little) hard to tap to bring up the menu...
Given the problems you've reported getting the FS button to work reliably, I'm not sure it'd help. I'll look at adding some tuning for the sensitivity of the popup menu, which might help. I fon't find any problem getting it to show though - I usually use my fingernail.
yes but my fs has been very easy if you recall it was due (I believe) to an issue with not having navigation enabled.
anyway lets say that (which it is not for me anymore) hard to use fs...well once you hit it you may as well be rewarded with more options right?
actually the reason I asked is because I was walking using fbreader this morning and had to stop every time I needed the menu, yet could use the toggle fs while walking.
btw for the close app in the menu if you do include it...would it be possible to make it require either an extra long press or a double tap while leaving the other chioces unchanged?
again I can't stress enough my appreciation enough, its guys like you and martink (modrana) that are keeping this device fresh...
ps having a button to access the menu could just be an option meaning someone else could still opt for fs instead right?
could double tap screen be an option to bring up the menu? that seems like it would require less sensitivity then holding the finger/stylus...I don't know if it is used for anything else, but I for one have never (purposely) double tapped anything in fbreader.
Hey, Rob1n, could you remove the scrollbar from the library view or, rather, make it optional? I think there was an option in the settings saying "show scrollbar" - the library view should make use of it.
Hey, Rob1n, could you remove the scrollbar from the library view or, rather, make it optional? I think there was an option in the settings saying "show scrollbar" - the library view should make use of it.
I don't see any setting in there for that, but I can certainly add one in.
EDIT: Currently I'm working on clearing up the issues reported by Valgrind - hopefully this'll eliminate the segfault on exit, and possibly it'll help with the Diablo lockup issue as well.
