Willem,
try removing Q_INVOKABLE before VendorModel() method. Withouth this
moc-related "keyword" VendorModel() method will remain "visible" to moc
since it is declared as a READ-accessor inside corresponding Q_PROPERTY
macro.
On Fri, Feb 12, 2016 at 9:29 AM Willem Ferguson <
willemfergu...@zoolog
I include an image explaining much of the context of the problem I
encounter.
I have a QML combobox that needs to respond to a C++ QStringListModel. I
do this as follows:
At the start where the QML machine is initialised (at the top of the
attached image)
1) Define and instantiate the underl
Hello,
The only reason to subclass one of Qt's QXxxxPrivate classes is if you're
> developing something as part of Qt.
>
> If you're feeling adventurous, you may want to access one of those classes,
> without deriving from them. But you're still accessing private API and
> you're
> subject to the
On quinta-feira, 11 de fevereiro de 2016 09:50:58 PST Israel Brewster wrote:
> QSettings settings("israelbrewster","epunchclockstd");
>
> and then use it. However, even if I call sync(), no settings file is ever
> created, and every time I create a settings object, I get an empty one -
> none of t
On quinta-feira, 11 de fevereiro de 2016 20:01:08 PST Nye wrote:
> Hello,
> It seems some elaboration is in order to explain why I've done that the way
> I did.
The only reason to subclass one of Qt's QXxxxPrivate classes is if you're
developing something as part of Qt.
If you're feeling adventu
On Feb 11, 2016, at 9:50 AM, Israel Brewster wrote:
>
> I have an app I built using Qt 5.5.1 on Mac OS X 10.11.1 (and perhaps other
> versions, but that's where I'm testing), which is sandboxed. When I run the
> app, it creates the sandbox directory just fine, however QSettings never
> creates
I have an app I built using Qt 5.5.1 on Mac OS X 10.11.1 (and perhaps other versions, but that's where I'm testing), which is sandboxed. When I run the app, it creates the sandbox directory just fine, however QSettings never creates the settings file. I am using QSettings at its most basic form, th
Hello,
It seems some elaboration is in order to explain why I've done that the way
I did. I'm wrapping around the OpenMPI library for purposes of running the
particular library with my applications on a cluster. What I'm trying to
achieve is to have the MPI messages come as events through Qt's even
On 11/02/16 15:45, Nye wrote:
> You should not have done that.
How come? I shouldn't have derived from QCoreApplication or shouldn't
have used the private API?
Don't use the private APIs. If you want to create a QCoreApplication
subclass, simply derive from that. Same for every other class.
Hello all,
We have a Qt Quick application on Android that we are trying to profile. In
particular we are interested in the VRAM usage of the application.
Utilizing Android's "dumpsys gfxinfo" command outputs a steady amount of used
memory regardless of additional objects rendered on screen. Thi
Hi,
We would definitely like to extend our offering with some sort of tooltips and
notification banners in the future. We might prefer stick to the terminology Qt
and Qt Quick have used in the past, so we probably won't end up calling them
snackbars, toasts, or anything else as delicious, thoug
> You should not have done that.
How come? I shouldn't have derived from QCoreApplication or shouldn't have
used the private API?
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
sorry, was an old link - this one is the actual one:
https://www.google.com/design/spec/components/snackbars-toasts.html
Am 11.02.16 um 10:39 schrieb ekke:
> Hi,
>
> are there any plans to provide Snackbars and Toasts out of the box ?
> http://blog.chengyunfeng.com/design/spec/components/snackbars
Hi,
are there any plans to provide Snackbars and Toasts out of the box ?
http://blog.chengyunfeng.com/design/spec/components/snackbars-and-toasts.html
or do I have to implement them by trying to customize existing controls ?
thx
--
ekke (ekkehard gentz)
independent software architect
interna
14 matches
Mail list logo