Hi all.
As I can see, the QLockFile opens a lock-file with the 0644 permissions
in Linux, e.g. see QLockFile::LockError QLockFilePrivate::tryLock_sys() [1].
That means that only one user (owner) can modify this file. But it leads
to problems, for example, when this use-case:
1. User 'A' cre
Excellent summary. I'd like to add one point: The crashes appear to happen with
a big majority in qtbase.
Outside of qtbase I've only seen moc crash, on macOS I think.
Simon
From: Development on
behalf of Friedemann Kleint
Sent: Wednesday, July 27, 2016 8:
Hi,
to summarize for Windows:
- Crashes have been observed over time in various tests, mostly in
QtCore (QDir,QFile, QProcess see fex
https://bugreports.qt.io/browse/QTBUG-47370
- It only affects 64bit (!) (correct me if you have observed otherwise)
- It never has been observed for MinGW (m
Thinks for reply, nice of you.
I have an application that based on MFC MDI and it call 300+ DLLs(based on
MFC, type is MFC regular DLL, each DLL contains GUI based on Dialog, and
each DLL send && receive messages with MFC MDI application, as a plugin
cowork with the MFC MDI application). for some
I migrated to Qt from InterViews:
http://www.ivtools.org/ivtools/doc/refman3.1/index.html which used
floating-point units that could be arbitrarily rescaled, but default to points,
like many other standards (e.g., SVG, Postscript). I always found it strange
that Qt used integer pixel coords.
On quarta-feira, 27 de julho de 2016 05:56:52 PDT Nikita Krupenko wrote:
> 2016-07-27 4:02 GMT+03:00 Thiago Macieira :
> > Em quarta-feira, 27 de julho de 2016, às 02:49:31 PDT, Nikita Krupenko
> >
> > escreveu:
> >> In Material Design guidelines [1] all font sizes are in scaleable
> >> pixels (sp
2016-07-27 4:02 GMT+03:00 Thiago Macieira :
> Em quarta-feira, 27 de julho de 2016, às 02:49:31 PDT, Nikita Krupenko
> escreveu:
>> In Material Design guidelines [1] all font sizes are in scaleable
>> pixels (sp). So this size could be multiplied by some factor and all
>> fonts should scale equally
Em quarta-feira, 27 de julho de 2016, às 02:49:31 PDT, Nikita Krupenko
escreveu:
> In Material Design guidelines [1] all font sizes are in scaleable
> pixels (sp). So this size could be multiplied by some factor and all
> fonts should scale equally.
Maybe we should instead use a size calculated i
2016-07-19 15:58 GMT+03:00 Shawn Rutledge :
>> App should remember of couse this setting to restore it back at restart
>
> How should Qt encourage this? So far we have QSettings, but you need to
> define your own setting. And we have not made it easy to scale all fonts
> simultaneously, interac
Em terça-feira, 26 de julho de 2016, às 23:24:21 PDT, Giuseppe D'Angelo
escreveu:
> On Mon, Jul 25, 2016 at 5:51 PM, Thiago Macieira
>
> wrote:
> > Let's pay attention of what crashes and where. But we'll need to reproduce
> > this in order to debug it.
>
> It just happened again:
>
> http://t
On 26 July 2016 at 22:33, Henry Skoglund wrote:
> Hi, most likely I've had too much coffee, but has anyone checked if these
> intermittent crashes are due to outside DDOS/some trying to introduce a
> race condition and injecting new code into Qt's codebase?
>
The CI machines aren't internet acc
Hi, most likely I've had too much coffee, but has anyone checked if
these intermittent crashes are due to outside DDOS/some trying to
introduce a race condition and injecting new code into Qt's codebase?
Rgrds Henry
On 2016-07-26 23:24, Giuseppe D'Angelo wrote:
On Mon, Jul 25, 2016 at 5:51 P
On Mon, Jul 25, 2016 at 5:51 PM, Thiago Macieira
wrote:
>
> Let's pay attention of what crashes and where. But we'll need to reproduce
> this in order to debug it.
It just happened again:
http://testresults.qt.io/logs/qt/qtbase/ddfe2ba984be5d652fe500f6695040959db98fa4/OSXOSX_10_11x86_64OSXOSX_10
Em terça-feira, 26 de julho de 2016, às 20:08:30 PDT, BogDan Vatra escreveu:
> scoped enums are declared differenty : enum *class* MyEnum :)
> Even more, scoped enums in C++ must me used with fully qualified name
> *MyEnum a = MyEnum.Val1* not *MyEnum a = Val1*, so a scoped enum is not
> exacly a
2016-07-26 18:42 GMT+01:00 Alexander Nassian :
> Hi Andrea,
>
> Good proposal! But one little hint: The current behavior is not that
> confusing as you describe. On iOS and OS X for example the current behavior
> is normal.
>
>
Thanks Alexander!
And thanks for your input, that's exactly the kind
On 7/20/16, 5:12 AM, "Development on behalf of Edward Welbourne"
wrote:
>
>Then again, our SVG support is embarrassingly poor,
Especially when it doesn’t support clip path. Which I imagine will be vital for
icon designs.
___
Development mailing lis
On Dienstag, 26. Juli 2016 08:33:31 CEST Thiago Macieira wrote:
> Em terça-feira, 26 de julho de 2016, às 17:50:38 PDT, BogDan Vatra escreveu:
> > Hi,
> >
> > Is there any reason why C++11 scoped enums are not scoped in QML ?
>
> There's no trait to tell apart a scoped enum from an unscoped one.
Hi Andrea,
Good proposal! But one little hint: The current behavior is not that confusing
as you describe. On iOS and OS X for example the current behavior is normal.
Beste Grüße / Best regards,
Alexander Nassian
http://www.bitshift-dynamics.de
> Am 26.07.2016 um 16:12 schrieb Andrea Bernabei
On marți, 26 iulie 2016 08:33:31 EEST Thiago Macieira wrote:
> Em terça-feira, 26 de julho de 2016, às 17:50:38 PDT, BogDan Vatra escreveu:
> > Hi,
> >
> > Is there any reason why C++11 scoped enums are not scoped in QML ?
>
> There's no trait to tell apart a scoped enum from an unscoped one. An
Em terça-feira, 26 de julho de 2016, às 17:41:01 PDT, Giuseppe D'Angelo
escreveu:
> On Tue, Jul 26, 2016 at 5:33 PM, Thiago Macieira
>
> wrote:
> > This is all the engine sees. It's an enum.
>
> But moc might help in this, extracting the relevant information
> alongside the enum's metadata.
>
On Tue, Jul 26, 2016 at 5:33 PM, Thiago Macieira
wrote:
> This is all the engine sees. It's an enum.
But moc might help in this, extracting the relevant information
alongside the enum's metadata.
Also if std::is_enum::value is true and std::is_convertible::type>::value is false, then the enum
is
Hi,
No objection per-se, but we'd have to figure out some details. For example
declarative instantiation is
not an object, as the ownership rules do not comply with QObject. That would
leave us with a JavaScript
constructor function, replacing Qt.point(...) for example. But then we'd have
to
Em terça-feira, 26 de julho de 2016, às 17:50:38 PDT, BogDan Vatra escreveu:
> Hi,
>
> Is there any reason why C++11 scoped enums are not scoped in QML ?
There's no trait to tell apart a scoped enum from an unscoped one. An enum is
en enum, that's all.
If you want a given enum to be scoped in Q
Hi,
Is there any reason why I can only use Q_GADGETs objects in QML, but not to
create them?
It will be nice if we can register Q_GADGETs as qml creatable types too.
Cheers,
BogDan.
___
Development mailing list
Development@qt-project.org
http://lists
Em terça-feira, 26 de julho de 2016, às 11:22:04 PDT, Jędrzej Nowacki
escreveu:
> > # 11: DllUnregisterServer() - 0x7FF8DB7097B0
> > # 12: DllUnregisterServer() - 0x7FF8DB7097B0
> > # 13: DllUnregisterServer() - 0x7FF8DB7097B0
> > # 14: DllGetActivationFactory() - 0x7FF8DC9D1860
>
Hello,
I'd like to be able to register some "global" enums/flags to QML. I checked a
little bit how Qt does with all the enums from Qt namespace (qnamespace.h) and
I end-up in qqmlbuiltinfunctions which does all the "magic" which can't be
used by normal developers/libs.
Because I think having
Hi,
Thanks for the super quick reply !
I created a bug report for you here https://bugreports.qt.io/browse/
QTBUG-54961 .
Cheers,
BogDan.
On marți, 26 iulie 2016 14:54:46 EEST Simon Hausmann wrote:
> Hi,
>
>
> By the time this aspect of the QML engine was implemented, C++11 scoped
> enums did
Hi,
By the time this aspect of the QML engine was implemented, C++11 scoped enums
did not exist. I think it would be fine
to add this feature to the JavaScript bindings for C++ classes.
Simon
From: Development on
behalf of BogDan Vatra
Sent: Tuesday, July
Hi,
Is there any reason why C++11 scoped enums are not scoped in QML ?
If I have something like the following code in C++
class MyClass : public QObject
{
Q_OBJECT
public:
enum class MyEnum : uint16_t {
Val1,
Val2,
}
Q_ENUM(MyEnum)
);
// register the class
I'd like to use it in QML a
Sure, you could add something like that on top once the basic multiple QScreen
support is in place. (for HDMI at least, replicating more or less what
'tvservice' does. Not sure what (if any) API you have for other type of
displays, though.)
Laszlo
From: Develo
Hello everyone,
I'd like to propose changing the default value of QML Flickable's
flickableDirection in Qt 5.8.
The current default value is Flickable.AutoFlickDirection
The description is: it "allows flicking vertically if the *contentHeight*
is not equal to the *height* of the Flickable. Allows
Hi,
Am 07/26/2016 um 03:33 PM schrieb Laszlo Agocs:
> Lack of contributions and suitable hardware setup. There was a patch for
> making the target screen configurable via an environment variable which
> never made it to integration. We are now reviving it for 5.6 at
> https://codereview.qt-project
Lack of contributions and suitable hardware setup. There was a patch for making
the target screen configurable via an environment variable which never made it
to integration. We are now reviving it for 5.6 at
https://codereview.qt-project.org/#/c/166117/
Additional patches for discovering and
Ok, many thanks.
2016-07-26 14:51 GMT+03:00 Marc Mutz :
> On Tuesday 26 July 2016 14:41:25 Denis Shienkov wrote:
> > Hi all, Thiago.
> >
> > Seems, we (I'am) have missed default parameters for the waitFor() methods
> > of QSerialPort:
> >
> > * https://codereview.qt-project.org/#/c/165583/
> >
>
On Tuesday 26 July 2016 14:41:25 Denis Shienkov wrote:
> Hi all, Thiago.
>
> Seems, we (I'am) have missed default parameters for the waitFor() methods
> of QSerialPort:
>
> * https://codereview.qt-project.org/#/c/165583/
>
> So, my questions:
>
> 1. Is it possible just to add of a missed defaul
Hi all, Thiago.
Seems, we (I'am) have missed default parameters for the waitFor() methods
of QSerialPort:
* https://codereview.qt-project.org/#/c/165583/
So, my questions:
1. Is it possible just to add of a missed default params and to merge it?
2. If yes, then, what of a branch is makes sense?
Hi,
Are you trying to run the example on Android? If so, try to make a
simple Qt3D example with a QML Scene3D object, like this:
https://doc.qt.io/qt-5/qt3d-scene3d-example.html
I have had some trouble with running the other Qt3D examples on Android,
but I have not seen the same error messag
On Monday 25 of July 2016 10:27:30 Thiago Macieira wrote:
> On segunda-feira, 25 de julho de 2016 08:51:36 PDT Thiago Macieira wrote:
> > On segunda-feira, 25 de julho de 2016 14:07:04 PDT Jędrzej Nowacki wrote:
> > > Ugh I haven't seen link.exe crashing, but in case of moc I have
> > > impression
38 matches
Mail list logo
