On Thursday 09 January 2014 02:14 Robin Burchell wrote: > > On Wednesday 08 January 2014 09:22 Jonni Rainisto wrote: > >> If QStandardPaths points to wrong directory then its a bug > >> which should be fixed.
> On 09 Jan 2014, at 00:37, Thomas Tanghus <tho...@tanghus.net> wrote: > > Can we consider this as a (semi-)official answer? I would also say that > > harbour applications should not be rejected because of a (seemingly) > > Qt-bug that should be easily patchable i.e. that QStandardPaths.data > > doesn't reflect XDG-* standards. > I’m not sure I understand what bug you’re talking about. See the source: > On Thursday 09 January 2014 09:38 Wim de Vries wrote: > I am not sure, but maybe I caused the misunderstanding. > My app (code) uses QStandardPaths, but was rejected. > Harbour stated that I should use the XDG- based rules. > So, I thought: what is wrong with QStandardPaths? > Now -thanks to the comments up here- I understand that harbour was > talking about the .yaml/rpm stuff, not the directory references in the > app itself. My bad, I misunderstood. It looked like the app was being rejected because QStandardPaths returned empty|invalid paths. -- Med venlig hilsen / Best Regards Thomas Tanghus _______________________________________________ SailfishOS.org Devel mailing list
