On 11/12/13 17:20, Hamish Moffatt wrote:
> Hi,
>
> We use Assistant in our OSX app as a help viewer, and I'm trying to get
> our app to run sandboxed so we can submit it to the App store. (Qt 4.8.5.)
>
> We include the Assistant binary from our Qt build into our application
> bundle, passing it -co
Hi,
my application uses sqlite for its data and I modeled some complex relations
for customers, appointments and so on.
Now I want to edit such a relation using a custom dialog where the
appointments go to a list and some other stuff to a table (all are
QSqlTableModels).
The problem is: How d
> I was a bit confused about that one, it has to be done like this, right?
> It's an attached signal handler, so...
>
> Component {
>id: myDelegate
>Item {
>
> ListView.onAdd: {
> // here it is, but what is the index?
> }
>}
> }
>
> If i use that, what's the index t
On Wednesday, 11 December 2013 17:36:36 CEST, Philipp Kursawe wrote:
> In code that would be a loop over pX->sourceModel while the sourceModel
is
> a QAbstractProxyModel.
That's very similar to what I do in my code, too -- just loop as long as
the qobject_cast(translated.model()) is not a
nullp
When you have complex chain of ProxyModels you cannot use the result index
from a call to mapToSource because you cannot know how many proxy models
are down the chain.
Imagine this chain:
p2 -> p1 -> m0
pX are Proxy models, m0 is the base model.
I know only about p2 in my part of the code and wa
On quarta-feira, 11 de dezembro de 2013 14:02:16, Jan Kundrát wrote:
> It does make a difference -- running `make` did not produce any more object
> files after the build failed for the first time (with plenty of targets
> still not being built), while `make all` did the right thing.
Did you clean
On Wednesday, 11 December 2013 04:07:17 CEST, Thiago Macieira wrote:
>> - Why is `make first` the default target instead of `make all`?
>
> Because, as its name says, "first" is the first target.
>
> But it doesn't make a difference, does it? Both targets should do the
same.
It does make a differ
>> i see. there is one further point that i'm a bit confused with:
>> according to the QMacNativeWidget documentation, the user has to
>> take care of delivering events from Cocoa to the QMacNativeWidget.
>> however it seems that this is actually done internally, because in
>> the example the qt wi
> QMacNativeWidget creates an NSView that you will insert in your view
> hierarchy. That NSView will receive mouse and keyboard events, like
> any other view, that will be forwarded to the QMacNativeWidget as Qt
> events. Other events, such as expose or update events, will be also
> forwarded to Qt
Hi
In my development team we have a 2 applications (one MFC based and one Qt
based) that communicate via tcp sockets.
All of our development team members can run these applications without problem,
however, when I run it on my PC the applications run very slowly and I get an
inordinate number of
Though you set the animation to running, it needs to sync up with the
renderthread for it to actually start. As you trigger the loader right away,
the animation doesn't actually get to start. If you change it into something
like this it will work:
ParallelAnimation {
id: ani
11 matches
Mail list logo
