On 10/26/2010 05:26 PM, Chris Rider wrote:
As you can tell from the log file, the close method is being called, but
not the dispose.
Do I need to dispose also? Couldn't really find enough documentation to
figure out *exactly* what those two methods entail. I kind of assumed it
was something lik
Please disregard / delete / etc this thread...
I am merging this to another post
On 10/26/2010 11:26 AM, Chris Rider wrote:
I'm just creating logs with a function (see below for example)
I'm pretty sure it isn't being referenced anywhere else. We are merely
using this to initiate opening of
(I previously posted something about Document Loader - that is now
revised and different, hence this post ~~ You'll find this post much
more informative, I hope!)
Please forgive me for causing any confusion... I was put on this project
after another engineer here took another position, so I'v
I'm just creating logs with a function (see below for example)
I'm pretty sure it isn't being referenced anywhere else. We are merely
using this to initiate opening of the file.
Here is my C++ function...
void Cleanup(const Reference &component) {
WriteLog( "pid: %d - Cleanup\n", getpid
Although I am ignorant in much of this, I do have some random thoughts.
Mathias Bauer mentioned allowing the container to control changes for
some items (such as he did with notes2), but that this may be a problem
with larger objects such as graphics objects and even OLE objects. On
the other
Hi Frank,
Frank Schönheit wrote:
For the moment, I declared an UndoFailedException, derived from
css.uno.Exception, and let undo/redo throw it. Still an euphemism for
"anything can go wrong", though, so I am not that happy with it ...
I think a new UndoFailedException is better than css.uno.E
On 10/26/10 11:48, Frank Schönheit wrote:
I think any kind of error can happen inside an undo implementation for a
single action, so I can't think of any reasonable limitation here. A
WrappedTargetException might be appropriate, but then again, this is
just an euphemism for "anything can happen".
Hi Stephan,
>> I think any kind of error can happen inside an undo implementation for a
>> single action, so I can't think of any reasonable limitation here. A
>> WrappedTargetException might be appropriate, but then again, this is
>> just an euphemism for "anything can happen".
>
> I see it diff
Hi,
Il 26/10/2010 05:33, Pivithuru Wijegunawardana ha scritto:
Hi,
I am searching for a JPanel in java like performing dialog control in
Openoffice to contain some other controls inside. And this control model
should be able to make visible and invisible such that the controls inside
it also d
On 10/25/2010 07:10 PM, Chris Rider wrote:
We are using DocumentLoader to manage the opening of PowerPoint files,
and have recently discovered what appears to be a memory leak.
As a quick background, these are self-advancing presentations, created
using Microsoft by the end-user, who then uses o
On 10/18/2010 05:16 PM, Malte Timmermann wrote:
Or implementations w/o support for ref counting: For example, each
EditEngine Undo action needs to have an EditEngine*.
And EditEngines in OOo are destroyed and re-created quite frequently.
Maybe using an own Undo manager for the EditEngine is wr
11 matches
Mail list logo