Hi,
Currently we have these 2 functions in qobject.cpp:
extern "C" Q_CORE_EXPORT void qt_addObject(QObject *)
{}
extern "C" Q_CORE_EXPORT void qt_removeObject(QObject *)
{}
The qt_addObject is being called in the QObject constructor and
qt_removeObject in the destructor.
It seems that they ar
On 03/20/2012 10:55 AM, ext Adriano Rezende wrote:
> On 03/15/2012 10:43 AM, ext Shawn Rutledge wrote:
>>> I agree. I think this is the best solution given the deadline. It
>>> will not break any apps and we can get rid of this event synthesis
>>> for good. Is there a
On 03/15/2012 10:43 AM, ext Shawn Rutledge wrote:
>> I agree. I think this is the best solution given the deadline. It
>> will not break any apps and we can get rid of this event synthesis
>> for good. Is there anybody already working on this fix? Br, Adriano
> Yes, so far I just got the MouseAr
On 03/15/2012 04:15 AM, Jones Martin (Nokia-MP/Brisbane) wrote:
> Sure, if you don't touch the flag you don't break anything, but as soon as
> someone uses the flag somewhere in a hierarchy of interactive Items you're
> going to have problems. It's too late for 5.0.
We are already having proble
On Fri, Feb 3, 2012 at 3:26 PM, wrote:
>
> >> On Thursday 15 December 2011 18:40:45 Jesus Sanchez-Palencia wrote:
> >>> Hi there,
> >>>
> >>> I would like to gather your opinion on whether we should move
> >>> QUndoStack and QUndoCommand out of QtWidgets so they could be used
> >>> without requir
2011/11/21 Alan Alpert :
> On Tue, 22 Nov 2011 09:10:14 ext Adriano Rezende wrote:
>> Yes, I mean if QtQuick2 is designed to reduce memory footprint for
>> non-ui applications it makes sense to keep UI components in a separate
>> module. I'm just arguing that if the Windo
IOW, something like:
import QtQuick 2.0 // or QtQuick.UI 2.0 (if it makes sense)
Window {
}
- Adriano
2011/11/21 Adriano Rezende :
> 2011/11/21 Alan Alpert :
>> On Tue, 22 Nov 2011 00:50:28 you wrote:
>>> 2011/11/21 Alan Alpert :
>>> > On Mon, 21 Nov 2011
2011/11/21 Alan Alpert :
> On Tue, 22 Nov 2011 00:50:28 you wrote:
>> 2011/11/21 Alan Alpert :
>> > On Mon, 21 Nov 2011 17:26:44 ext Alan Alpert wrote:
>> >> On Tue, 15 Nov 2011 19:24:50 ext Alan Alpert wrote:
>> >> > Window{ //Not inheriting QQuickItem, creates a new top level window.
>> >> >
>> >
2011/11/21 Alan Alpert :
> On Mon, 21 Nov 2011 17:26:44 ext Alan Alpert wrote:
>> On Tue, 15 Nov 2011 19:24:50 ext Alan Alpert wrote:
>> > Window{ //Not inheriting QQuickItem, creates a new top level window.
>> >
>> > property int x
>> > property int y
>> > property int width
>> > p
On Fri, Nov 11, 2011 at 2:45 AM, Alan Alpert wrote:
> On Fri, 11 Nov 2011 05:01:32 ext Adriano Rezende wrote:
> > I think the Window element should not inherit from QQuickItem, since
>> it's not an element in the render tree; it's basically a window
>> represe
On Mon, Nov 7, 2011 at 5:32 AM, Alan Alpert wrote:
> Given that there can be Desktop Components providing the full API for desktop
> windows (and this is being discussed on the qt-components ML already), I
> propose the following minimal Window{} API for QML core (i.e. inside the
> QtDeclarative l
11 matches
Mail list logo
