Re: [Interest] QDatastream, QMap, QImage serialization

On Monday, 21 May 2018 15:50:02 -03 Jason H wrote: > I don't think C++ has a good concept of what it is that I want to do. C++ > does not allow multiple return types from functions, therefore, the only > way to get the type you want returned is provide an overload with different > parameters. What

Re: [Interest] QDatastream, QMap, QImage serialization

On 05/21/2018 10:53 AM, Thiago Macieira wrote: On Sunday, 20 May 2018 21:27:31 -03 Jason H wrote: Why is QImage even a GUI type? "Has pixels" is the simplest defintiion of GUI. Not exactly a definition which should actually be used though. While facial recognition may make for impressive dis

Re: [Interest] QDatastream, QMap, QImage serialization

> > On Monday, 21 May 2018 13:04:00 -03 Jason H wrote: > > which makes me think it should be T texture(); > > THAT is not going to happen. > > Find a non-template name and we can talk. I don't think C++ has a good concept of what it is that I want to do. C++ does not allow multiple return types

Re: [Interest] QDatastream, QMap, QImage serialization

On Monday, 21 May 2018 11:46:54 -03 Christoph Feck wrote: > Maybe for Qt6 we could have a thin QtGuiCore library, which manipulates > image data and colors, but does not have a dependency on GUI servers > (OpenGL, X11, etc.) I think even that name was proposed before. I don't remember if it was du

Re: [Interest] QDatastream, QMap, QImage serialization

On Monday, 21 May 2018 11:03:38 -03 Jason H wrote: > Going through the list of Qt GUI classes, there are several that I think > should be moved: QImage > QStandardItem* > Matrix and Vector classes > QPdfWriter > QPen, QBrush, etc. > QText* QTextDocument et al. > QValidator et al. > QFont* (where ap

Re: [Interest] QDatastream, QMap, QImage serialization

On Monday, 21 May 2018 13:04:00 -03 Jason H wrote: > which makes me think it should be T texture(); THAT is not going to happen. Find a non-template name and we can talk. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center __

Re: [Interest] Qt5 CSS StyleSheet Variables

This was the route I was in the process of designing up with a combination of JSON to store the values that we want to allow users to change. Thank you for the verification of the process. Mike Jackson -Original Message- From: Interest on behalf of Tony Rietwyk Date: Monday, May 21

Re: [Interest] QDatastream, QMap, QImage serialization

I can definintely understand if people don't want pixel depenencies in their QCoreApplication. But I cringe a labeling it GUI. It's graphical but it's not necessarily User and definately not interface. I'd call it "graphics" or something. If you say GUI I'm thinking a display device and input dev

Re: [Interest] QDatastream, QMap, QImage serialization

> * QPaintDevice has the concept of "physical DPI" and "logical DPI" which are > GUI-related. > * QPainter depends on QPaintEngine which depends on QPaintDevice > * QPen depends on QBrush which depends on QPixmap > * QPen and QBrush are useless without QPainter > * QImage inherits QPaintDev

Re: [Interest] QDatastream, QMap, QImage serialization

On Mon, May 21, 2018 at 5:46 PM, Christoph Feck wrote: > > Maybe for Qt6 we could have a thin QtGuiCore library, which manipulates > image data and colors, but does not have a dependency on GUI servers > (OpenGL, X11, etc.) This makes most sense to me. I wouldn't really want the core, which is a

Re: [Interest] Qt5 CSS StyleSheet Variables

Hi Mike, QStyleSheets are pretty limited, so we: - load a sass file from Qt resources, - inject some calculated variables at the start relating to the specific app and client screen size, - process the sass to css - set the output into QApplication. This occurs at startup, and whenever the

Re: [Interest] QDatastream, QMap, QImage serialization

> "Has pixels" is the simplest defintiion of GUI. plenty of programs working with pixels don't have GUIs. Stuff like imagemagick, pdftk, ffmpeg, etc etc ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/intere

Re: [Interest] Qt5 CSS StyleSheet Variables

Am 21.05.2018 um 15:47 schrieb Michael Jackson: Just to confirm, but does Qt accept CSS variables as describe here: ? I tried and I get the error that the style sheet could not be parsed. I have a style sheet with a LOT of color settings and h

Re: [Interest] QDatastream, QMap, QImage serialization

-Original Message- From: Interest on behalf of Thiago Macieira Organization: Intel Corporation Date: Monday, May 21, 2018 at 9:49 AM To: Subject: Re: [Interest] QDatastream, QMap, QImage serialization On Sunday, 20 May 2018 21:27:31 -03 Jason H wrote: > Why is QImage even a GUI

Re: [Interest] QDatastream, QMap, QImage serialization

-Original Message- From: Interest on behalf of Sze Howe Koh Date: Monday, May 21, 2018 at 10:17 AM To: interest Subject: Re: [Interest] QDatastream, QMap, QImage serialization On 21 May 2018 at 17:08, Christian Gagneraud wrote: > On 21 May 2018 at 20:12, Jean-Michaël Celeri

Re: [Interest] QDatastream, QMap, QImage serialization

On 21.05.2018 16:36, Murphy, Sean wrote: Why is QImage even a GUI type? "Has pixels" is the simplest defintiion of GUI. As a counter to that: QImage be safely used outside of the GUI thread which is not true for most classes that are considered GUI classes... But doesn't QImage need PNG to

Re: [Interest] QDatastream, QMap, QImage serialization

> > Why is QImage even a GUI type? > > "Has pixels" is the simplest defintiion of GUI. As a counter to that: QImage be safely used outside of the GUI thread which is not true for most classes that are considered GUI classes... Sean This message has been scanned for malware by Forcepoint. www.f

Re: [Interest] QDatastream, QMap, QImage serialization

On 21 May 2018 at 17:08, Christian Gagneraud wrote: > On 21 May 2018 at 20:12, Jean-Michaël Celerier > wrote: >>> Why is QImage even a GUI type? 99% of what I do with QImage is not for >>> GUI. I can understand that QPixmap is GUI, but to me QImage is i/o and >>> pixel/metadata manipulation (usin

Re: [Interest] QDatastream, QMap, QImage serialization

Going through the list of Qt GUI classes, there are several that I think should be moved: QImage QStandardItem* Matrix and Vector classes QPdfWriter QPen, QBrush, etc. QText* QTextDocument et al. QValidator et al. QFont* (where applicable. QFontDatabase, QRawFont) Various geometrics (QPolygon, QRe

Re: [Interest] QDatastream, QMap, QImage serialization

On Mon, May 21, 2018 at 9:49 AM Thiago Macieira wrote: > On Sunday, 20 May 2018 21:27:31 -03 Jason H wrote: > > Why is QImage even a GUI type? > > "Has pixels" is the simplest defintiion of GUI. > GUI is more than that - it involves displaying said pixels. Otherwise it's just data. If you look

Re: [Interest] QDatastream, QMap, QImage serialization

On Sunday, 20 May 2018 21:27:31 -03 Jason H wrote: > Why is QImage even a GUI type? "Has pixels" is the simplest defintiion of GUI. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ I

[Interest] Qt5 CSS StyleSheet Variables

Just to confirm, but does Qt accept CSS variables as describe here: ? I tried and I get the error that the style sheet could not be parsed. I have a style sheet with a LOT of color settings and having to do a bunch of search/replace to change t

[Interest] qt 5.11 and above qml window patches

Hello, Current patches add functionality for movement and resizing of frameless windows using qml only functionality, see: https://github.com/johanhelsing/qt-csd-demo Above implements the movement. I am wondering how resizing would be proper. Is there a way to address all edge-lines of an Applica

Re: [Interest] QDatastream, QMap, QImage serialization

On 21 May 2018 at 20:12, Jean-Michaël Celerier wrote: >> Why is QImage even a GUI type? 99% of what I do with QImage is not for >> GUI. I can understand that QPixmap is GUI, but to me QImage is i/o and >> pixel/metadata manipulation (using scanline() where appropriate) . Yes, >> occasionally I use

Re: [Interest] QDatastream, QMap, QImage serialization

> Why is QImage even a GUI type? 99% of what I do with QImage is not for GUI. I can understand that QPixmap is GUI, but to me QImage is i/o and pixel/metadata manipulation (using scanline() where appropriate) . Yes, occasionally I use a QPainter on one, but that does not beed to be bound to a windo