@Mike:
> What you write now seem to be first making an impression you are trying
to debug something, then immediately declare you ...
don't think too much about me, just try to pick up the matter itself,
> You may ask for help in some specific technical problem (like "I'm debugging
function Foo using gdb; ...
i try to find the point why a subsequent save of the same file has different - non odf 1.2 compliant - content. imho the read in of the first save has a bug, i couldn't yet spot which module does do this read in, i'm suspecting xmlfilti.cxx, but even if i'd find the working path and do some changes in it, that might be wrong if the actual workflow is wrong in general ... e.g. wrong filtering routine used ... read in of range and filter definition interact with each other and i'd make two bugs instead of one (i assume that happend to get the ui-buttons working) ... whatever ... thus a little 'pro help' would be nice,
> "I'm looking for the function that implements spreadsheet function KLM; how can I find it?").
i'm looking for the function that reads an *.ods file and implements the range and filter definitions in the runtime memory representation, as well for access by the gui (buttons) as by macros (basic),
>> - point me to the last 'unthreaded' version,
> None ever existed.
will check that ...
my questions in the last mail are neither sequent nor ordered or exclusive, just pick any, some or all, i'd like to not to talk about my attempts too long, but find a way to the matter itself,
it becomes quite more urgent as:
- any changes might produce compatibility problems for previous saved files,
- LO 7.0 will change to odf 1.3 format? that would be a unique opportunity to fix this problem at least for new files before! many files are produced which would get compatibility problems,
reg.
Bernhard
---
@Mike:
> Please don't reply privately. Having done so, instead of replying to the
ok, your mail contained a request for encrypted communication, that leaded me to the idea you'd like private mail,
> It creates threads always; it need multiple threads, and there's no "single-threaded LibreOffice".
:-( would be much easier for debugging of logical errors, already think to get a single core machine to reduce threading ... or use old LO version for logical and workflow analyzing,
> You need to tell where - at which stage - are you now,
i'm trying to bring down a bug with wrong save of filtering conditions in odf format, last status there:
https://bugs.documentfoundation.org/show_bug.cgi?id=133336
help could be:
- take the bug(s) and fix it (i'm much better in finding new ones than fixing),
- recheck the bug(s), and point me if i'm on error, or the way to fix,
- tell me the path reading and writing filtering conditions and ranges take through the modules and routine calls, the path they shall! take, maybe it's odd right now?
- a howto for easy and comfortable debugging, my state: gdb - difficult to catch threads, edb - difficult to point to what i'd like to see, ddd - unusable reg. small fonts on highdpi display, kdevelop - frequent and too many crashes, ... which environment do 'pros' use? VS? (win was my first attempt, stuck in 32/64 bit conflict of something),
- find the guy or girl who shortly commented about 'wrongly exported' in XMLExportDataPilot.cxx, maybe (s)he is on the right trail,
- point me to the last 'unthreaded' version,
regards, tia for any help,
b.
P.S. i'm not subscribed to the list, answers private if possible,
> What you write now seem to be first making an impression you are trying
to debug something, then immediately declare you ...
don't think too much about me, just try to pick up the matter itself,
> You may ask for help in some specific technical problem (like "I'm debugging
function Foo using gdb; ...
i try to find the point why a subsequent save of the same file has different - non odf 1.2 compliant - content. imho the read in of the first save has a bug, i couldn't yet spot which module does do this read in, i'm suspecting xmlfilti.cxx, but even if i'd find the working path and do some changes in it, that might be wrong if the actual workflow is wrong in general ... e.g. wrong filtering routine used ... read in of range and filter definition interact with each other and i'd make two bugs instead of one (i assume that happend to get the ui-buttons working) ... whatever ... thus a little 'pro help' would be nice,
> "I'm looking for the function that implements spreadsheet function KLM; how can I find it?").
i'm looking for the function that reads an *.ods file and implements the range and filter definitions in the runtime memory representation, as well for access by the gui (buttons) as by macros (basic),
>> - point me to the last 'unthreaded' version,
> None ever existed.
will check that ...
my questions in the last mail are neither sequent nor ordered or exclusive, just pick any, some or all, i'd like to not to talk about my attempts too long, but find a way to the matter itself,
it becomes quite more urgent as:
- any changes might produce compatibility problems for previous saved files,
- LO 7.0 will change to odf 1.3 format? that would be a unique opportunity to fix this problem at least for new files before! many files are produced which would get compatibility problems,
reg.
Bernhard
---
@Mike:
> Please don't reply privately. Having done so, instead of replying to the
> It creates threads always; it need multiple threads, and there's no "single-threaded LibreOffice".
:-( would be much easier for debugging of logical errors, already think to get a single core machine to reduce threading ... or use old LO version for logical and workflow analyzing,
> You need to tell where - at which stage - are you now,
i'm trying to bring down a bug with wrong save of filtering conditions in odf format, last status there:
https://bugs.documentfoundation.org/show_bug.cgi?id=133336
help could be:
- take the bug(s) and fix it (i'm much better in finding new ones than fixing),
- recheck the bug(s), and point me if i'm on error, or the way to fix,
- tell me the path reading and writing filtering conditions and ranges take through the modules and routine calls, the path they shall! take, maybe it's odd right now?
- a howto for easy and comfortable debugging, my state: gdb - difficult to catch threads, edb - difficult to point to what i'd like to see, ddd - unusable reg. small fonts on highdpi display, kdevelop - frequent and too many crashes, ... which environment do 'pros' use? VS? (win was my first attempt, stuck in 32/64 bit conflict of something),
- find the guy or girl who shortly commented about 'wrongly exported' in XMLExportDataPilot.cxx, maybe (s)he is on the right trail,
- point me to the last 'unthreaded' version,
regards, tia for any help,
b.
P.S. i'm not subscribed to the list, answers private if possible,
_______________________________________________ LibreOffice mailing list LibreOffice@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/libreoffice
