Problem description: In macros Libre Office, operators EMPTY and NOT_EMPTY does not run correctly. In the two cases, return all records Steps to reproduce: sub FiltrePlage(NomZone as String, Col as integer) dim Plage as object, Filtre as object dim ChampFiltre(0) As New com.sun.star.sheet.TableFilterField 'Accès à une plage de données par son nom Plage = thiscomponent.DatabaseRanges.getByName(NomZone) 'Crée un descripteur de filtre vide sur la plage référencée Filtre = Plage.referredCells.createFilterDescriptor(true) with Filtre .ContainsHeader = true 'La 1ère ligne = en-tête de colonnes .UseRegularExpressions = True 'Utilise les expressions régulières end with with ChampFiltre(0) .Field = Col .Operator =com.sun.star.sheet.FilterOperator.EMPTY end with Filtre.setFilterFields(ChampFiltre()) 'Passe les paramètres Plage.referredCells.filter(Filtre) 'Applique le filtre Current behavior: returns all records Expected behavior: Operating System: Windows (other) Version: 3.6.4.3 release Last worked in: 3.6.3.2 release
Can you please tell us in which version it worked?
It worked with Windows 8 and Libre Office 3.6.4 > Message du 26/12/12 20:00 > De : bugzilla-daemon@freedesktop.org > A : philippe.schmidlin@orange.fr > Copie à : > Objet : [Bug 58520] FILTER: Operators filter EMPTY and NOT_EMPTY > > > Comment # 1 on bug 58520 from Markus Mohrhard Can you please tell us in which version it worked? You are receiving this mail because: You reported the bug.
(In reply to comment #2) > It worked with Windows 8 and Libre Office 3.6.4 > Why do you report the bug then against version 3.6.4?
The bug is existing en 3.6.3 and windows 8 Before, I'll never work in Libre Office because I'll work with Windows XP SP3 and Microsoft Office 97 > Message du 27/12/12 03:32 > De : bugzilla-daemon@freedesktop.org > A : philippe.schmidlin@orange.fr > Copie à : > Objet : [Bug 58520] FILTER: Operators filter EMPTY and NOT_EMPTY > > > Comment # 3 on bug 58520 from Markus Mohrhard (In reply to comment #2) > It worked with Windows 8 and Libre Office 3.6.4 > Why do you report the bug then against version 3.6.4? You are receiving this mail because: You reported the bug.
set RESOLVED WORKSFORME per comment 2 Please change status of this bug to: REOPENED if that problem still persists in latest stable release