[Interest] QTableView behavior; word wrapping plus rows resize to content

2018-12-13 Thread Bernhard Lindner
Hi!

I am using a QTableView with word wrapping enabled and rows configured to 
resize to
content automatically.

Is it desired behavior that the view a does NOT update the row height when 
columns are
manually resized in a way that a cell changes from single-line to double-line 
text (or
vice versa)?

The following line solves the problem:

CHECK_TRUE(connect(ui->tableView->horizontalHeader(), 
SIGNAL(sectionResized(int, int,
int)), ui->tableView, SLOT(resizeRowsToContents(;

However it seems strange that the above does not work out of the box. Is that 
behaviour a
bug?

-- 
Best Regards, 
Bernhard

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] Qt strategy WRT OpenGL support on OSX moving forward

2018-12-13 Thread Laszlo Agocs
Hi Lachlan,


Yes, there are some efforts on-going around this. The existing OpenGL enablers 
are not going anywhere anytime soon, but going forward the strategy for Qt and 
its core 2D/3D offering is going to be slightly different. Instead of depending 
on OpenGL directly, a wider variety of graphics APIs will be embraced via 
appropiate abstraction layers. For Apple platforms this means Metal of course.


Various bits and pieces are currently in research phase, targeting mainly Qt 6, 
with some parts possibly making it to later Qt 5 releases, if the need arises. 
Expect more news around this during next year.


Best regards,

Laszlo



From: Interest  on behalf of 
lachlan.hether...@data61.csiro.au 
Sent: Thursday, December 13, 2018 12:32 AM
To: jh...@gmx.com
Cc: inter...@lists.qt-project.org
Subject: Re: [Interest] Qt strategy WRT OpenGL support on OSX moving forward


Thanks.



Lachlan Hetherton

Senior Software Engineer

DATA61 | CSIRO

E lachlan.hether...@data61.csiro.au

T +61 3 9545 8041

www.data61.csiro.au





From: Jason H 
Date: Thursday, 13 December 2018 at 9:40 am
To: "Hetherton, Lachlan (Data61, Docklands GS)" 

Cc: "inter...@lists.qt-project.org" 
Subject: Re: [Interest] Qt strategy WRT OpenGL support on OSX moving forward



http://blog.qt.io/blog/2018/05/30/vulkan-for-qt-on-macos/



Sent: Tuesday, December 11, 2018 at 12:06 AM
From: lachlan.hether...@data61.csiro.au
To: inter...@lists.qt-project.org
Subject: [Interest] Qt strategy WRT OpenGL support on OSX moving forward

Hi there,



Apologies if this has been asked recently – I have not been tracking the 
mailing list recently but could not find a comprehensive response anywhere 
else. Apple have deprecated OpenGL from OSX 10.14 (Mojave), presumably in an 
attempt to move developers onto their Metal platform. What is Qt’s strategy for 
this moving forward? Is there a plan to move away from offering OpenGL 
functionality in the Qt API since it will no longer be available across all 
platforms? Or is there an intention to provide an OpenGL (or Vulkan) 
implementation built on Metal?



Thanks – once again apologies if this has already recently been covered.



Regards,



Lachlan Hetherton

Senior Software Engineer | Workspace

CSIRO | Data61

E lachlan.hether...@data61.csiro.au T +61 3 9545 8041

Door 34, Goods shed north, Village Street, Docklands, VIC 3008

www.data61.csiro.au

PLEASE NOTE
The information contained in this email may be confidential or privileged. Any 
unauthorised use or disclosure is prohibited. If you have received this email 
in error, please delete it immediately and notify the sender by return email. 
Thank you. To the extent permitted by law, CSIRO does not represent, warrant 
and/or guarantee that the integrity of this communication has been maintained 
or that the communication is free of errors, virus, interception or 
interference.

Please consider the environment before printing this email.

[Data61 | CSIRO logo]



___ Interest mailing list 
inter...@lists.qt-project.org https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] Android IRC channels

2018-12-13 Thread Giuseppe D'Angelo via Interest

Il 13/12/18 10:56, Shawn Rutledge ha scritto:
I would suggest switching to #qt-android permanently, because it follows 
the pattern (we have a lot of #qt-foo channels), whereas necessitas was 
the name of the Qt 4 port to Android. https://necessitas.kde.org/ says 
"Necessitas project was completely merged 
 
into Qt project and KDE Free Qt Foundation Agreement 
 was 
amended  to cover Qt for 
Android Port 
. 
  We suggest you all to to switch to Qt5.” So it seems to me the name is 
obsolete for us, but people could still hang out there and discuss 
issues with other versions (such as the Qt 4 version).


Side note: on Freenode you can simply set one channel to forward to the 
other.


My 2 c,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts



smime.p7s
Description: Firma crittografica S/MIME
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] Android IRC channels

2018-12-13 Thread Shawn Rutledge
I would suggest switching to #qt-android permanently, because it follows the 
pattern (we have a lot of #qt-foo channels), whereas necessitas was the name of 
the Qt 4 port to Android.  https://necessitas.kde.org/ says "Necessitas project 
was completely 
merged
 into Qt project and KDE Free Qt Foundation 
Agreement was 
amended to cover Qt for Android 
Port.
  We suggest you all to to switch to Qt5.” So it seems to me the name is 
obsolete for us, but people could still hang out there and discuss issues with 
other versions (such as the Qt 4 version).
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


Re: [Interest] Android IRC channels

2018-12-13 Thread Mitch Curtis
> -Original Message-
> From: André Pönitz 
> Sent: Wednesday, 12 December 2018 8:43 PM
> To: Mitch Curtis 
> Cc: interest@qt-project.org
> Subject: Re: [Interest] Android IRC channels
> 
> On Wed, Dec 12, 2018 at 07:45:58AM +, Mitch Curtis wrote:
> > We have #necessitas for Android discussion,
> 
> Right.
> 
> > and I remember #qtforandroid was recently created after the spam
> > attacks.  Today I learned we also have #qt-android.
> 
> #qt-android has been the hideout during the spam attack.
> 
> I was not aware of #qtforandroid until today.
> 
> > Can we please settle on one channel [...]
> 
> * Channel #necessitas modes: +cnt
> * Channel #necessitas created on Wed Apr 27 06:39:36 2011
> 20 users
> 
> * Channel #qt-android modes: +ns
> * Channel #qt-android created on Thu Aug 17 06:42:20 2017
> 16 users
> 
> * Channel #qtforandroid modes: +cnrt
> * Channel #qtforandroid created on Fri Aug 31 09:15:36 2018
> 1 user
> 
> 
> #necessitas wins by age, population and openness. A potential problem
> there is the lack of an operator as seen during the attack, in which case #qt-
> android is a reasonable alternative to keep around.

necessitas is not a very good or memorable name for "Qt for Android". Being 
apparently susceptible to spam attacks doesn't sound great either.

Regardless of which one we choose: why don't we decide as a community to settle 
on one? Is there a reason to have three or even two for the same purpose?

> > and I'll add it to the Wiki [1]?
> 
> > People looking for help don't benefit from having three fragmented
> > channels for discussion.
> >
> > [1] https://wiki.qt.io/Online_Communities
> 
> There was no fragmentation this morning. #necessitas was the only channel
> listed in the wiki. Someone added #qtforandroid in the mean time, which
> now has been replaced by a recommendation to use #qt-android.

So what you're saying is... there is no fragmentation if people aren't aware of 
the other two duplicate channels?

In that case, the best course of action would be continue having 2-3 channels 
and remove all but one from the Wiki. I'm starting to get the hang of this 
now... does this also work for documentation? Users don't need to know it if we 
don't add it to the docs? This actually explains a lot. :)

> Andre'
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest