Michael Polak wrote:
>
> Well, if I change F9 key to just "dump virtual screen", the results will
> be same as in Netscape. But F9 is more than just "Refresh" in Netscape; it
> should correct even broken virtual screens. In fact, after F9 key, virtual
> screens are deallocated, and Arachne refreshes screen in no-virtual
> screen mode...
>
> I can add some kind of Alt+F9 which would just dump virtual screen,
> and don't refresh GUI or generate virtual screen again.
>
> You were simply comparing two different features, as F9 in Arachne is
> currently not comparable to Netscape's View | Refresh function.
Hello Michael;
I was not using virtual screens so that extra delay was not in the result.
My original report commented:
Just doing a page down takes the same time in Arachne as the initial load
- say 5.5 seconds - while Netscape does it in about a third of a second.
That's 18 times faster !
So, let us ignore the "F9" function and look at the above case of page down.
Don't waste all that time correcting broken virtual screens. To speed up
the local interface, don't do ANY more than necessary on a page down/up.
You are saying, in effect, that you don't trust the results of rendering so
you are doing it again. Once is enough. Even on refresh.
If the screen becomes corrupt, let the user make the decision to reload.
And please, no altF9 unless you switch the functions.
i.e. altF9 = current F9 function, New F9 function is FAST refresh.
But you don't really need both. Just simplify the current function.
Only my opinion of course.<G>
- Clarence Verge
--
- Help stamp out FATWARE. As a start visit: http://home.arachne.cz/
--
