On Sat, May 7, 2016 at 2:29 AM, Nye wrote:
> I don't see any multiple inheritance that forms a diamond. And although I
> like the older syntax better, I don't see what's the problem with the new
> syntax here. This:
>
You're right, my example didn't suffer from the diamond inheritance
problem. B
1. Could you tell me please how one can set custom geometry for QSGClipNode
(not the rectangular one)? Should I just create QSGeometry with
QSGGeometry::defaultAttributes_Point2D() attribute and add vertices? Will
Scene Graph recognize that polygon is closed (I need clipping to have a
form of circl
2016-05-07 22:12 GMT+02:00 Elvis Stansvik :
> 2016-05-07 21:39 GMT+02:00 Elvis Stansvik :
>> Hi all,
>>
>> Back in 2010 there were a couple of interesting threads on this list
>> regarding the use of state machines:
>>
>> http://comments.gmane.org/gmane.comp.lib.qt.general/29861
>> http://c
2016-05-07 21:39 GMT+02:00 Elvis Stansvik :
> Hi all,
>
> Back in 2010 there were a couple of interesting threads on this list
> regarding the use of state machines:
>
> http://comments.gmane.org/gmane.comp.lib.qt.general/29861
> http://comments.gmane.org/gmane.comp.lib.qt.general/36760
>
>
Hi all,
Back in 2010 there were a couple of interesting threads on this list
regarding the use of state machines:
http://comments.gmane.org/gmane.comp.lib.qt.general/29861
http://comments.gmane.org/gmane.comp.lib.qt.general/36760
In the second one, which was about using a C++ QStateMachi
2016-05-07 18:43 GMT+02:00 Elvis Stansvik :
> 2016-05-07 16:56 GMT+02:00 Mark Gaiser :
>> On Sat, May 7, 2016 at 3:44 PM, Elvis Stansvik wrote:
>>>
>>> 2016-05-07 15:27 GMT+02:00 Elvis Stansvik :
>>> > Hi all,
>>> >
>>> > Maybe I'm doing something completely wrong, but on Qt 4.8.7, this
>>> > work
2016-05-07 16:56 GMT+02:00 Mark Gaiser :
> On Sat, May 7, 2016 at 3:44 PM, Elvis Stansvik wrote:
>>
>> 2016-05-07 15:27 GMT+02:00 Elvis Stansvik :
>> > Hi all,
>> >
>> > Maybe I'm doing something completely wrong, but on Qt 4.8.7, this
>> > works (pressing Ctrl+O prints "clicked"):
>> >
>> > test.
On Sat, May 7, 2016 at 3:44 PM, Elvis Stansvik wrote:
> 2016-05-07 15:27 GMT+02:00 Elvis Stansvik :
> > Hi all,
> >
> > Maybe I'm doing something completely wrong, but on Qt 4.8.7, this
> > works (pressing Ctrl+O prints "clicked"):
> >
> > test.cpp:
> >
> > #include
> > #include
> > #include
>
Hi,
Re: https://codereview.qt-project.org/#/c/140954/
Is the justification for omitting .pc files still relevant that "frameworks are
currently broken anyway"? They don't appear to be, but omitting pkg-config
files for them makes it impossible to build all dependent software that uses
pkg-conf
2016-05-07 15:27 GMT+02:00 Elvis Stansvik :
> Hi all,
>
> Maybe I'm doing something completely wrong, but on Qt 4.8.7, this
> works (pressing Ctrl+O prints "clicked"):
>
> test.cpp:
>
> #include
> #include
> #include
> #include
> #include
>
> class MainWindow : public QMainWindow {
> Q_OBJ
2016-05-07 15:27 GMT+02:00 Elvis Stansvik :
> Hi all,
>
> Maybe I'm doing something completely wrong, but on Qt 4.8.7, this
> works (pressing Ctrl+O prints "clicked"):
>
> test.cpp:
>
> #include
> #include
> #include
> #include
> #include
>
> class MainWindow : public QMainWindow {
> Q_OBJ
Hi all,
Maybe I'm doing something completely wrong, but on Qt 4.8.7, this
works (pressing Ctrl+O prints "clicked"):
test.cpp:
#include
#include
#include
#include
#include
class MainWindow : public QMainWindow {
Q_OBJECT
public:
MainWindow(QWidget *parent = 0) : QMainWindow(parent)
Ok I solved an other problem.
So, if somebody has the same problem:
Use add_library($PROJECT_NAME} SHARED...) instead of
add_executable($PROJECT_NAME} SHARED...) since on the android it is only a
shared library and not an executable.
> Am 06.05.2016 um 17:56 schrieb NoRulez :
>
> Hi ekke,
>
The more interesting thing here is doing react-native with a Qt(Quick)
rendering engine / back-end (so you end up with a web stack that can
render to a scene graph ways faster than a browser engine, while not
having to maintain QML in your tech stack). React really is the
equivalent of QML in t
To make it work with black images the formule should be that :
gl_FragColor = (tex + color) * qt_Opacity;
But your color must have alpha at 0 else you'll loose the alpha of the
texture.
Here is the bug of graphical rendering issue when using graphical effects :
https://bugreports.qt.io/browse
Am 07.05.16 um 11:48 schrieb Xavier Bigand:
> Your image is black because the shader is multiplying the color. You
> should do your image sources in white to get the correct result.
for Google's Material Icons it's no problem: they're provided in black
and white,
but iOS icons from other sources us
2016-05-07 11:32 GMT+02:00 Elvis Stansvik :
> Hi all,
>
> In a fullscreen page-based embedded QML app (HMI), I find myself often
> wanting to disable all signal connections when the page is not active
> (on top of stack).
>
> I found this 5 year old bug:
>
> https://bugreports.qt.io/browse/QTBU
Your image is black because the shader is multiplying the color. You should
do your image sources in white to get the correct result.
You can also change the operation in the line :
gl_FragColor = tex * color * qt_Opacity;
As I know if you are using a GraphicalEffect by image you'll have the sam
Hi all,
In a fullscreen page-based embedded QML app (HMI), I find myself often
wanting to disable all signal connections when the page is not active
(on top of stack).
I found this 5 year old bug:
https://bugreports.qt.io/browse/QTBUG-18245
I think Daniel's analysis in the comments is very
PS.
I just realized you're worried that the functions are virtual. Well this is
of no consequence, the vtable is respected (if I remember correctly that's
specified in the standard). So the following should also be working without
any problem:
QObject::connect(a, Interface::someSignal, b, Interfac
On Sat, May 7, 2016 at 10:34 AM, d3fault wrote:
> Nobody's mentioned that Qt4-style connect syntax is required to solve the
> diamond inheritance problem that frequently appears when using a
> signals/slots interface.
> [snippet]
>
I don't see any multiple inheritance that forms a diamond. And a
@ Xavier: the ToolButton Image still is black, but perhaps I did
something wrong. It's the first time I used a ShaderEffect
Do you really think it could cause problems on Android / iOS apps ?
Images are small images
@ J-P: ColorOverlay works well and also looks easier to understand for
mobile devs
2016-05-07 10:20 GMT+02:00 J-P Nurmi :
>> On 06 May 2016, at 23:27, Elvis Stansvik wrote:
>>
>> 2016-05-06 22:41 GMT+02:00 J-P Nurmi :
>>>
>>>
>>> The Stack.status property must be attached to an item that is in a
>>> StackView. In the snippet above, it is attached to the Connections element.
>>
> On 06 May 2016, at 23:27, Elvis Stansvik wrote:
>
> 2016-05-06 22:41 GMT+02:00 J-P Nurmi :
>>
>>
>> The Stack.status property must be attached to an item that is in a
>> StackView. In the snippet above, it is attached to the Connections element.
>> You can give the Rectangle element an id t
Nobody's mentioned that Qt4-style connect syntax is required to solve the
diamond inheritance problem that frequently appears when using a
signals/slots interface.
Ex:
class Interface
{
public:
virtual QObject* asQObject()=0;
protected: //signals
virtual void someSignal()=0;
public: //slo
25 matches
Mail list logo
