01/23/2013, 08:03 AM
|
#901 (permalink) |
|
Member
![]() |
shneor. Presumably you have it full screened? If so, touch and hold the top of the screen until the menu bar appears and then swipe down on the left and choose "Go Back".
If you have the menu bar, just swipe and go . . . . . . Last edited by MikeN68; 01/23/2013 at 08:03 AM. Reason: being silly! |
01/23/2013, 02:43 PM
|
#902 (permalink) | |
|
Member
![]()
Posts: 1,334
|
Quote:
Shneor
__________________
Shneor Pre 3 on T-Mobile, 32gb Touchpad |
|
01/24/2013, 12:24 PM
|
#903 (permalink) |
|
Member
![]() ![]()
Posts: 712
|
Hi, just as a late heads-up:
With the newest version, you can also just quickly "swipe" over the screen from right to left. That will also let you go back. If not, you may need to go into the preferences screen and select one of the default input assignments again. Or you can customize the "Go back" action to an input method of your liking. |
01/25/2013, 01:17 AM
|
#904 (permalink) | |
|
Member
![]()
Posts: 70
|
Quote:
hope this helps ! Achim |
|
02/16/2013, 04:50 PM
|
#905 (permalink) |
|
Member
![]()
Posts: 105
|
I just got a new epub ebook which loads and can be read perfectly in pReader JS, but shows no content in pReader native alpha. The bookmarks are imported correctly, but I dont't see any text. The issue occurs on my Pre3, I didn't try other devices yet.
I can send you a PM with a link to the file in my dropbox. I would prefer not to post this link to the public, as the ebook is a commercially purchased one. I would be very happy, if you could find the error. Many thanks for your great app, and for your continuing support for webOS! Kind regards Carsten Last edited by ZehHa; 02/17/2013 at 05:12 PM. |
03/04/2013, 12:31 PM
|
#906 (permalink) | |
|
Member
Posts: 157
|
Quote:
Sadly I tried to read a book in native, which snagged into a picture and stopped. The js version had text decoding issues and rendered some characters differently. I have confirmed this as if you use the belt bar to advance past pictures in a book, close the application, then reopen it, you would be able to read the book in native. The same text differed but native was correct, javascript was not -- Sent from my Palm Pre using Forums
__________________
Proud user of a Palm Pre+ on T-Mobile running 1.4.5 in New Orleans, Louisiana -- Need some help getting Odamex on WebOS Remember the bombardment of letters WebOS users hopefully sent to HP? Well, we need you again loyal users. Click and sign to entertain the slight notion of this petition reaching LG. The numbers rise daily, we need to keep going! Even if its slim to none, its better than doing nothing and complaining! |
|
03/05/2013, 03:52 PM
|
#907 (permalink) |
|
Member
![]() ![]()
Posts: 712
|
Hi Shadowflank.
Thanks for your bug report. I have already received several similar bug reports; so I'm reasonably convinced that they're all due to the same bug or set of bugs in the code. So in and of itself, it should be quickly fixable. The main problem is time, though. Or rather, the lack of it on my side. Given that several projects at work (at Intel, for those who are interested) have entered their productive phase at pretty much the same time means that my free time tends to go towards zero during the week. Today, for example, I was at home around 21:00. Long experience has taught me that trying to code after that watershed only causes more bugs. Weekends are really the only time were I have enough free time to do something; but between going skiing, having relatives over, going out with friends and -- most recently -- polishing up my French knowledge for the next summer vacation, I usually only have 1-2 hours per week where I can actually work on non-work-related coding. In other words: Yes, I'm still working on fixing these bugs; but progress is sadly rather slow. ![]() Anyway, I'll keep you guys and gals posted on when I can reliably say that I can publish a next release; hopefully sooner rather than later.
|
05/13/2013, 02:26 PM
|
#910 (permalink) |
|
Member
![]() ![]()
Posts: 712
|
Hi there.
The reports of my death; or that of this app; have been slightly exaggerated. ![]() I have made a bit of progress in the last few weeks (months; actually). The most major point: Smooth autoscroll now works -- and that with only a slight additional drain on the battery. The reason why progress is glacially slow is due to the fact that my current workload at Intel does not leave me much free time during the working week to do much progress; so only the weekends remain. Add to that the fact that in the last 2 months, almost every second week was a 4-day working week thanks to perfectly aligning public holidays in Bavaria. Add to that, that on a good chunk of weekends I'm busy doing stuff with and to friends and colleagues -- which was a non-issue when I was a student since we pretty much partied-out during the week back then. ![]() Add to that, that I was back in Berlin with my family 4 times in the last 2 months to attend: 4 birthdays (including my own), two weddings and one funeral. Add to that the 2 further birthdays (among them a 1st and a 30th) in the coming 2 months; along with two more weddings of close friends (it spreads like an epidemy, I tell ya!) So from 30 days each month; I am lucky if I can currently spend even half a day on further development of the pReader. But I do still want to add a handful of features before I decide on whether or not to retire its development. ![]() In short: It's not time for the fat lady to sing just yet.
|
05/16/2013, 05:13 AM
|
#911 (permalink) | |
|
Member
![]()
Posts: 70
|
Quote:
good to hear that you and your Baby are still alive. Remember, you have biggest responsibility for the live of your baby, since it is the only ebook-reader for Webos which deserves this name.Thanks for your ongoing support and ...... what about your wedding plans ? Infected too?Chears Achim from Gießen in Germany |
|
![]() |
|
| Thread Tools | |
| Display Modes | |
|
|



