Thanks Ulf. I think that is exactly what we need.
I tried out the following. but I was having some trouble accessing the
pointer to the dataModel. Am I on the right track?
*SCXML:*
*liondatamodel.h:*
#include "qscxmlcppdatamodel.h"
class LionDataModel: public QScxmlCppDataModel
{
Q_OBJEC
Thiago Macieira wrote:
> The point is that before we can have this conversation about Qt, you need to
> convince the Chromium developers of the need to share the internals with other
> frameworks and retain binary compatibility.
Of course, but in turn it wouldn't be of much use to start such a di
> In the example above, how would we get access to Event parameter for "state1"
> and "state5"?
You can access the event currently being processed via the data model. The
EcmaScript data model has a readonly property "_event" and the C++ data model
has a method scxmlEvent(). The null data model
Hi,
I try without succes to attribute a statusTip on Qaction in a QmenurBar who
works if the Qaction is enabled or disabled...
Impossible... When the Qaction is enabled, no problem but when it's disabled...
I tryed to use eventFilter on :
- the Qaction : No event.
- the Qmenu : some event (no
Hi,
Is it exist a simple solusion for auto resize the background image of a
QtableWidgetItem ?
For now, I use the resizeEvent who calculate the cell size and resend a Qpixmap
with the good size.
It's not really userfriendly :p
Any simple idea ?
Best regards.
Hizo
___
Hi,
We are in the process of migrating from QStateMachine to QT SCXML on QT
5.8.
For example, we have the following stateMachine where the same event drives
multiple transitions in the stateMachine,
with C++ implementing the programmatic hooks like connectToState and
connectToEvent.
SCXML:
On Freitag, 16. März 2018 13:43:53 CET Mike Krus wrote:
> Hi
>
> > On 16 Mar 2018, at 08:04, Martin Koller wrote:
> >
> > What are the possible file formats the QSceneLoader can load (Qt 5.10,
> > Linux openSuse 42.3) ?
> > Is blender among them ?
> SceneLoader uses Assimp internally for doing
On Friday, 16 March 2018 07:31:10 PDT René J.V. Bertin wrote:
> >* WebEngine needs patched Chromium source
>
> And that's not just because the Chromium library expects to be part of the
> (a) Chromium browser?
Yes.
The point is that before we can have this conversation about Qt, you need to
con
Neat! That works! Thanks!!
> Sent: Friday, March 16, 2018 at 10:28 AM
> From: "Nikolai Tasev"
> To: "Jason H"
> Cc: "Interestqt-project.org"
> Subject: Re: [Interest] QImage::Format_Grayscale8 work working
>
> Sorry a typo qRgb(qRed(rgbVal), qRed(rgbVal), qRed(rgbVal)) for setting
> the pixel
>* WebEngine needs patched Chromium source
And that's not just because the Chromium library expects to be part of the (a)
Chromium browser?
>* Chromium can be updated at any time and break Qt
Which applies to other dependencies as well (FFmpeg comes to mind...)
>WebView module allows using pla
Sorry a typo qRgb(qRed(rgbVal), qRed(rgbVal), qRed(rgbVal)) for setting
the pixel on the red channel
On 3/16/2018 4:25 PM, Nikolai Tasev wrote:
Yes that confirms my suspicions that setPixel for Format_Grayscale8
expect different things ( as I wrote in my previous email).
You need to pass qRgb(
Yes that confirms my suspicions that setPixel for Format_Grayscale8
expect different things ( as I wrote in my previous email).
You need to pass qRgb(qRed(rgbVal), 0, 0) for red, not qRed(rgbVal).
On 3/16/2018 4:09 PM, Jason H wrote:
5.10.1
Yes, that's a good idea. So I wrote some code:
5.10.1
Yes, that's a good idea. So I wrote some code:
QImage gray8 = color8(image, Qt::gray, QImage::Format_Grayscale8); //
modded my function to take the format.
QImage index = color8(image, Qt::gray, QImage::Format_Indexed8);
int differences = 0;
int same = 0;
I just looked the source code of setPixel() for Grayscale8. It
seems(there is a pixel converter, that needs more time to see in detail)
that for Grayscale8 you are supposed to give a 32 bit not an index like
in Indexed8. That is for white give , instead of
00FF(returned currently fr
Hi,
I would suggest solution number 1 (Creating a Custom Style).
To get the designer to show your custom style you have to configure it in
qtquickcontrols2.conf.
You can do this in the editable combo box in the form editor if
qtquickcontrols2.conf does exist.
You can refer to the Qt Quick
I am not sure if there any difference in how the Indexed8 and Grayscale8
are saved. It also depends on the
file format. As far as I remember many formats always save as 32bits.
First look at the pixel data as raw unsigned char values to see if the
conversion is correct, maybe the problem comes
Thanks.
I guess that means there is nothing I can do to make it work.
The issue seems to be that openssl supports 78 ciphers and the UWP
implementation only supports 4.
I have created a bugreport (https://bugreports.qt.io/browse/QTBUG-67112)
indicating the specific cipher I know is not working.
It returns black. All black. Hence the issue :-)
The original file is an 8MP 4:3 image as png it saves to ~10mb.
- as a Grayscale8 it saves as 8 KB-kilo. (should be 8,121,344)
- as Indexed8 it saves as 5.5mb
I'd expect Greyscale8 to be about the same size on disk as Indexed8 +/- color
table.
16.03.2018, 15:52, "René J. V. Bertin" :
> Thiago Macieira wrote:
>
>> Whom would we share it with?
>
> In that vision I had the question was more "whom would Chromium share itself
> with" :)
* WebEngine needs patched Chromium source
* Chromium can be updated at any time and break Qt
>
> In th
Thiago Macieira wrote:
> Whom would we share it with?
In that vision I had the question was more "whom would Chromium share itself
with" :)
In theory you could be sharing "it" with any other application built on
Chromium
but not Qt. A concrete example would be on mobile devices with their lim
Hi
> On 16 Mar 2018, at 08:04, Martin Koller wrote:
>
> What are the possible file formats the QSceneLoader can load (Qt 5.10, Linux
> openSuse 42.3) ?
> Is blender among them ?
SceneLoader uses Assimp internally for doing the actual parsing, please see [1]
for the list of
formats that support
What is not working for Grayscale? Looking at the code it will do
different things when you are passing Qt::red, Qt::blue, Qt::green.
It will not return a color image but a grayscale image of the
corresponding channel.
On 3/16/2018 2:08 PM, Jason H wrote:
Sent: Friday, March 16, 2018 at 9:12 A
> Sent: Friday, March 16, 2018 at 9:12 AM
> From: "Nikolai Tasev"
> To: "Jason H" , "Interestqt-project.org"
>
> Subject: Re: [Interest] QImage::Format_Grayscale8 work working
>
>
> Format_Indexed8 and Format_Grayscale8 both have 8bit per pixel. The
> difference is that to convert from the 8bi
Hi,
On 16/03/2018 07:06, Maurice Kalinowski wrote:
Hi,
I’ll let Oliver provide the detailed answer, but the history as such is:
* WinRT uses a new networking API. When released Winsock was not
only deprecated but disallowed to be used
* We implemented network features using that new
Format_Indexed8 and Format_Grayscale8 both have 8bit per pixel. The
difference is that to convert from the 8bit pixel to RGB values
(QImage::pixel() method)
for Indexed8u you need to set the Palette for conversion and for
Grayscale8 you don't (it just assumes that R=G=B=gray value)
Are you t
What are the possible file formats the QSceneLoader can load (Qt 5.10, Linux
openSuse 42.3) ?
Is blender among them ?
--
Best regards/Schöne Grüße
Martin
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?
() ascii ribbon campaign - against html e-mail
/\
26 matches
Mail list logo
