Veljko Miljanic wrote:
>
> I noticed that when Arachne 1.68 finish downloading image from a net
> just stops at the end and don't want to display it. You know: progres bar
> just stands on 100% and wait for something. Than when I press r it
> converts image to bmp and displayes it correctly.
This is download problem, for some reason, Arachne waits for connection
to close. I am trying to hunt bugs in HTTP module all the time...
> Someone here told that he thinks that Arachne graphic routines are to
> slow. Well in vesa modes(I use only them) they are fast but can be done
> eaven faster. I think that there are two things which are done wrong:
> -Drawing of the background. When Arachne draws small bacground image
> it have to repeat image over and over until it redraw hole screen. Metod
> for this which is implemented in Arachne is the worst one. Arachne
> algoritham(if I noticed right) at the first step draws first pixel of
> bacground image to evry place on the screen where some copy of bacground
This is not true, Arachne draw entire row of pixels, and this is fastest
way in which this can be done. If you want to copy entire block of
pixels, you would need to allocate more memory, and block copying is
anyway done row-by-row.
> -The second thing I wanted to talk about is routine for drawing the
> text. It is pretty fast but Arachne shoud implement something
> diferent. When drawing new page Arachne usualy redraws whole screen with
> background color and then writes text. Faster way to do this woud be that
> Arachne draws new text and clears background in the same time. And if page
> haves backround instead of clearing backroud Arachne could write backround
> image. I have done this on my computer and the speed up is about 20%
> to 30%. So I think it is worth of traying. Also you rendering of page woud
> be nicer.
Arachne is not cleaning the background it there is background image to
be displayed. Additionaly, with virtual screen turned on,
you won't even notice the effects you are talking about.
