On 05/07/2011 09:20 AM, Vladimir Nadvornik wrote:
> Hi,
>
> On St 4. května 2011, Omari Stephens wrote:
>> Howdy, all
>>
>> I'm poking around with the marks code. Currently, marks are _really
>> slow_ when you connect at least one mark to an image tag — when an image
>> with no marks drops to zero
On Sat, 7 May 2011 11:41:00 +0200, VN wrote:
> > FWIW, and considering that the current refcounting in Geeqie is
> > troublesome, you've got my blessing. :-) I'm all for a central list of
> > the current directory's file data objects, with added maintenance
> > structures on top of that.
>
> What
On Čt 5. května 2011, Michael Schwendt wrote:
> On Wed, 04 May 2011 16:30:44 +, OS wrote:
>
> > That said, I imagine that we'd be better off just always holding a ref
> > for every FileData in the current directory. On my machine, a FileData
> > is 176 bytes and a GList is 24 bytes, so for
Hi,
On St 4. května 2011, Omari Stephens wrote:
> Howdy, all
>
> I'm poking around with the marks code. Currently, marks are _really
> slow_ when you connect at least one mark to an image tag — when an image
> with no marks drops to zero refs, we lose track of what marks it may
> have, and on
On Wed, 04 May 2011 16:30:44 +, OS wrote:
> That said, I imagine that we'd be better off just always holding a ref
> for every FileData in the current directory. On my machine, a FileData
> is 176 bytes and a GList is 24 bytes, so for a directory of 20,000
> images, we'd be spending 3.8MB
Howdy, all
I'm poking around with the marks code. Currently, marks are _really
slow_ when you connect at least one mark to an image tag — when an image
with no marks drops to zero refs, we lose track of what marks it may
have, and on the next marks filtering op, we end up having to hit the
XM
