[Vm-dev] primitiveDisplayCharacters

Bert Freudenberg bert at freudenbergs.de
Wed Oct 17 00:49:46 UTC 2018

On Tue, Oct 16, 2018 at 4:59 PM Eliot Miranda <eliot.miranda at gmail.com>

> Hi All,
>     I notice that primitiveDisplayCharacters calls copyBits for each
> character when doing blits that don't use copyLoopPixMap (as recorded in
> the quickBlt variable).  That means for certain usages we're invoking
> lockSurfaces & unlockSurfaces for each character.  It would be
> straight-forward to hoist the (un)lockSurfaces sends out of the loop.  Is
> there any reason not too do this?  i..e is there any reason why one would
> want (un)lockSurfaces invoked on each character in the quickBlt == false
> case?

You would have to know the affected area in advance to lock all at once. It
that's easy to compute, sure.

Also, I'm not sure we're even using that primitive with the current fonts?

- Bert -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20181016/0cbf85a4/attachment.html>

More information about the Vm-dev mailing list