On 2018-11-15 17:07, Thiago Macieira wrote:
On Thursday, 15 November 2018 05:54:22 PST Manner Róbert wrote:
Hope it is useful for someone. To be honest, I always imagined that if
everyone would use UTF-8 life would be much better, now I'm unsure
Blame Apple for deciding to use an uncommon norm
I never have a' Original number" as the strings come from file names and
another app.
QCollator is the ticket.
Cheers,
frank
On 15/11/18 4:14 AM, Shawn Rutledge wrote:
On 14 Nov 2018, at 03:28, Frank Rueter | OHUfx wrote:
Hi,
I need to use the QSortFilterProxyModel to sort strings with numb
Ha, QCollator is the perfect solution, thank you!
I was not aware of that one.
Cheers,
frank
On 15/11/18 3:57 AM, Giuseppe D'Angelo via Interest wrote:
Hi,
Il 14/11/18 03:28, Frank Rueter | OHUfx ha scritto:
This works nicely but I’m wondering if it’s reliable and efficient to
implement it li
Yes, I can! The problem is when I close the app and start it again. The result
is null.
Data is not being persisted and I do t understand why... :(
--
Nuno Santos
No dia 15/11/2018, às 19:07, jlk escreveu:
> Hi Nuno,
>
>Can you save and restore a simple NSObject, say an NSString?. If so,
Hi Nuno,
Can you save and restore a simple NSObject, say an NSString?. If so,
your problem is probably with converting the QVariant to NSObject. I
have not used Qt with iOS yet so I don't have any deeper help than that,
sorry!
However, Maybe there are helper functions you need to write
Colin,
Thanks for your reply.
While you are right considering the code I have posted here, the truth is that
in my actual code I have the setObject. But since I have more stuff going on I
didn’t want to flood the list with code:
void Settings::setSharedKey(QString key, QVariant value)
{
if
Hi Nuno,
You are missing a line, something like:
[defaults setValue:object forKey:key]
in setSharedKey.
>
> From: Nuno Santos
> Subject: [Interest] Qt iOS / App Groups / NSUserDefaults initWithSuiteName /
> Not persisting
> Date: November 14, 2018 at 7:24:06 AM AST
> To: "interest@qt-pr
On Thursday, 15 November 2018 05:54:22 PST Manner Róbert wrote:
> Hope it is useful for someone. To be honest, I always imagined that if
> everyone would use UTF-8 life would be much better, now I'm unsure
Blame Apple for deciding to use an uncommon normalisation back in the day for
HFS. The HFS
QGuiApplication app(argc, argv);
QScreen *screen = app.screens()[0];
double dpi = screen->physicalDotsPerInch();
dpi-= dpi * 10/100;
if(dpi >= 640) dpi = dpi/640; //xxxhdpi
else if (dpi >= 480) dpi = dpi/480; //xxhdpi
else if (dpi >= 320
That I don't known, I'm 100% Qml and I just apply this to my Control style at
one place. Maybe there is a way to do this into the cascading widget style...
-Original Message-
From: Roman Wüger
Sent: November 14, 2018 1:32 PM
To: Jérôme Godbout
Cc: ekke ; interest@qt-project.org
Subject
Hi,
((
My local encoding is utf-8, so the source file seems to be the same as well:
> file main.cpp
main.cpp: c program text, UTF-8 Unicode text
))
I think I have found the bug which causes this:
https://bugreports.qt.io/browse/QTBUG-70732
I am currently working on a workaround, I am now able to
What is the encoding of your source file?
QString constructors interprets char* as if they are UTF-8. If the
source file is encoded in your local encoding, the QString created for
QFile constructor will have a wrong unicode storage of your wanted
filename, then will try to convert what it thinks is
12 matches
Mail list logo
