John Levon wrote:
> On Sat, Jun 07, 2003 at 08:53:59PM +0200, Alfredo Braunstein wrote:
>
>> Sure, the creation part. The problem is that newBuffer is called
>> internally by bufferlist.loadFile. I would need to make the client call
>> newBuffer()
>
> Well this sounds sensible to me
I will make
On Sat, Jun 07, 2003 at 08:53:59PM +0200, Alfredo Braunstein wrote:
> Sure, the creation part. The problem is that newBuffer is called internally
> by bufferlist.loadFile. I would need to make the client call newBuffer()
Well this sounds sensible to me
regards
john
John Levon wrote:
> On Fri, Jun 06, 2003 at 07:12:00PM +0200, Alfredo Braunstein wrote:
>
>> 3) Split the loading of the buffer from its creation, so the caller would
>> typically do:
>
> Isn't this what bufferlist.newBuffer() already does ?
Sure, the creation part. The problem is that newBuffe
On Fri, Jun 06, 2003 at 07:12:00PM +0200, Alfredo Braunstein wrote:
> 3) Split the loading of the buffer from its creation, so the caller would
> typically do:
Isn't this what bufferlist.newBuffer() already does ?
regards
john
Can we reach some consensus on what to do? I recall the options I remember
(if I understood them well... ;) :
1) Pass a bv to BufferList::loadLyXFile so it can be attached as soon as the
Buffer is created
2) Pass a slot to BufferList::loadLyXFile that can be attached to a signal
in Buffer to catc
