We know about the slowness bug - and of course it will be fixed. You
don't have to jump up and down and PROVE that it's broken. If you
asked the question "will it be improved?" then you must have expected
either anwser, if you didn't like the answer I gave then why did you
ask such a dumb question?
All bugs, as found by you and investigated by me, will be fixed eventually.
Please do not ask if they will be fixed. Please do not insist that they will
be fixed for your pleasure. Please do not plead for them to be fixed before
the next beta.
I've asked you nicely now :)
> page scroll, is terribly slow in V 3.3.117 and my 040@28 mhz.
> IBrowse and AWeb are much smoothly.
There is an issue which means that certain GUI operations will
not work as smoothly as possible on heavy sites (I can't describe what
"heavy" is to you very easily :) - it's effectively exactly the same
bug as the "slow table layout" bug, V sits doing something it
really needn't do so much, for every object on the page, and with
many table cells that's two objects (cell and group) so..
It will be fixed eventually. Don't ask when.
As for "IBrowse and AWeb do it better". Well... so what? So they
do things differently to Voyager. As it happens, Voyager supports
MUI 4 Smoothscrolling Virtgroups, which means clicking the
scrollbar will slide you down to the page position just like it would
in a smoothscrolling listview.
AWeb and IBrowse do not. Are you going to bug those authors
for this feature? Since V has it, surely they should too? Or maybe
if you like those browsers so much, you should just go and use
those exclusively, eh? :P
--
Matt
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
