I have committed several changes to the SwordReader repository. I have
done some polishing of the double buffering, still more to do but this
round includes discarding of taps and button presses while the text is
being loaded. I also gray/disable out the menubar as a visual queue that
something
Hi David
David Trotz wrote:
> I wanted to you to know that I do appreciate the feedback, as you are
> coming at it from a different approach and I never thought to be
> clicking all around the screen while waiting.
And I really appreciate all the work you're putting into this app.
e line. Let's get this right
> now.
>
> --
> In Christ,
> David
>
>
> -Original Message-
> From: Barry Drake <[EMAIL PROTECTED]>
> Sent: Friday, December 14, 2007 8:18 AM
> To: SWORD Developers' Collaboration Forum
> Subject: Re: [sword-devel]
it
slower and harder to optimize later on down the line. Let's get this right now.
--
In Christ,
David
-Original Message-
From: Barry Drake <[EMAIL PROTECTED]>
Sent: Friday, December 14, 2007 8:18 AM
To: SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] Sw
Hi there ..
DM Smith wrote:
> In another app, we put up a busy cursor and blocked input at the start
> of every event and restored the cursor and user input at it's end.
Thanks for that - sounds good to me. I think I'd prefer that approach
to any other, as it lets the user know to wait!
Barry Drake wrote:
> Hi David ...
>
> David Trotz wrote:
>
>> This is related to the above. All I can ask is that maybe you try it
>> on a real device,?
>>
> For the most part it's OK on my device. It works seamlessly, and
> doesn't give me time to find problems - that is, until I tu
Hi David ...
David Trotz wrote:
> This is related to the above. All I can ask is that maybe you try it
> on a real device,?
For the most part it's OK on my device. It works seamlessly, and
doesn't give me time to find problems - that is, until I turn on the
morphs, strongs or footnotes in
Barry,
I can see the advantage .. but it's broken something! On the ARM
emulator (remember that this is incredible slow, so you can see the
'stages' it goes through). On the ARM emulator, go to Matt 1:1 and turn
on morphs in kjv. It fairly quickly shows half a screen with the
morphs, b
Hi David
David Trotz wrote:
> Verse scrolling is now fixed and committed.
I've re-wound my stuff to rev. 57 from svn. The only file I'm working
on currently is simplenavigator.cpp. If you need to make changes to
that file, please liase first so we don't mess up.
God bless,
Barry
--
Hi David ...
David Trotz wrote:
> Verse scrolling is now fixed and committed.
I can see the advantage .. but it's broken something! On the ARM
emulator (remember that this is incredible slow, so you can see the
'stages' it goes through). On the ARM emulator, go to Matt 1:1 and turn
o
Verse scrolling is now fixed and committed.
-- David
David Trotz wrote:
> Hi all,
> I have been thinking of ways to improve the amount of time it takes for
> the display to show anything when changing the text. In some cases its
> as much as 4 seconds! So I decided to take an approach used often
Hi all,
I have been thinking of ways to improve the amount of time it takes for
the display to show anything when changing the text. In some cases its
as much as 4 seconds! So I decided to take an approach used often in
computer graphics, double buffering. In our case the buffer is an html
page
12 matches
Mail list logo