<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:newbie-02@gmx.de" title="b. <newbie-02@gmx.de>"> <span class="fn">b.</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - AUTOFILTER: in non functional after 'Copy Sheet' in new sheet"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=59312">bug 59312</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>newbie-02@gmx.de
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - AUTOFILTER: in non functional after 'Copy Sheet' in new sheet"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=59312#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - AUTOFILTER: in non functional after 'Copy Sheet' in new sheet"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=59312">bug 59312</a>
from <span class="vcard"><a class="email" href="mailto:newbie-02@gmx.de" title="b. <newbie-02@gmx.de>"> <span class="fn">b.</span></a>
</span></b>
<pre>for the Bug Hunting Session 7.0.0.0.a1+:
OP behaviour still repro,
same action (copy sheet with defined autofilter) with some other data works
ok!, you gain functioning autofilters in the copied sheet, e.g.
<a href="http://bugs.documentfoundation.org/attachment.cgi?id=56922">http://bugs.documentfoundation.org/attachment.cgi?id=56922</a> from #45958,
difference:
the file 'source.ods' for this bug has! a 'defined range' which the filter is
'mapped'? to,
('forfilters' defined with '<table:database-range table:name="forfilters"
table:target-range-address="Tabelle21.A1:Tabelle21.I9"
table:display-filter-buttons="true" table:orientation="column"/>' in
content.xml)
while 'example.ods' from #45958 doesn't have such a definition, and the filter
is mapped to an '__Anonymous_Sheet_DB__0',
(such database ranges are defined automatically when you apply an autofilter
which doesn't find a defined range to apply to, '<table:database-range
table:name="__Anonymous_Sheet_DB__0"
table:target-range-address="Hoja1.A1:Hoja1.C1048574"
table:display-filter-buttons="true"/>' in content.xml)
(forfilters does have a 'xml_tag'? table:orientation="column" which is applied
- mostly? - when re-saving a file after save-load cycle and is relevant for
other misinterpretations, e.g.
<a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - filesave: fileopen: macro: xml: calc filtered ranges wrongly saved in .ods format? xml export / import buggy? affects filters in database ranges with offset to cell A1"
href="show_bug.cgi?id=132488">https://bugs.documentfoundation.org/show_bug.cgi?id=132488</a> - dunno if that
steps in here too)
and! forfilters is a 'defined range' which is a name 'global to a document'?
and can:
- neither have multiple definitions with different 'scopes' like 'named ranges'
may have,
- nor is a 'per sheet' definition, as '__Anonymous_Sheet_DB__0' is, which as
well can have multiple definitions within one document, one per sheet, thanks
@Eike for clarification,
thus it's logically impossible to create an identical fully working copy of a
sheet with an autofilter defined referencing a 'defined range',
unless you e.g. work with new names like e.g. 'forfilters_01' ..., or define
and set 'scopes' for defined ranges, or other creative solutions,
be aware that the behaviour of #132488 messing around with the .field values
might step in for any development and tests of this problem ... i can't judge
this reg. very small knowledge about the structures and the code (in fact i
just stumbled across this bug when i was looking for the steps in which
'table:field-number=' and 'table:orientation="column"' are defined for the save
to file and are read back for runtime representation, any tips for that would
be highly appreciated - in #132488 o.c.),
all above looked for and said by a 'newbie', i apologize for any mistakes I may
have made ...
as well i apologize for the length of my contribution, I try to analyze and
present the situation clearly, i hope for 'old bugs' such an approach is
allowed,
maybe you should introduce a new category: 'currently not solveable' and
declare such bugs as enhancement requests?
simply omitting the filter buttons as suggested by the OP would not be a
solution in my opinion, the copy of the sheet would be incomplete,</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>