[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kimageshop
Subject:    Re: High-level pixel access methods
From:       Patrick Julien <freak () codepimps ! org>
Date:       2004-02-15 12:33:13
Message-ID: 200402150733.13774.freak () codepimps ! org
[Download RAW message or body]

On February 15, 2004 07:25 am, Boudewijn Rempt wrote:
> On Sunday 15 February 2004 10:16, Patrick Julien wrote:
> > Single pixel access from methods is always going to be slow, no matter
> > when they reside.
>
> But perhaps not as slow as they're now -- I think it's something that's
> really needed. The tile system should be hidden as much as possible from
> the rest of the system. And time and again, one needs to get a pixel, set a
> pixel -- it's what painting apps is all about.

I am not disputing this, nor am I trying to prevent having a getPixel and 
setPixel like functions.  Simply stating that placing these operations in 
KisTileMgr would result in an almost an identical implementation.  So, yes, 
they would be just as slow.

>
> > So, you basically want a way to access pixels on a line basis without
> > having to think about tiles?
>
> Yes -- and without having to allocate temporary memory buffers to copy
> the image data into before accessing it. Two examples:

Yes, I know, there is no need for further arguments, I agree, I'm trying to 
figure something using iterators.

The iterators would allow pointer like access to pixels while masking tile 
boundaries.

_______________________________________________
kimageshop mailing list
kimageshop@kde.org
https://mail.kde.org/mailman/listinfo/kimageshop
[prev in list] [next in list] [prev in thread] [next in thread]