Why doesn't the XCB platform plugin use _NET_WM_STATE_HIDDEN? There are a
number of bugs related to it QTBUG-31117, QTBUG-39376, QTBUG-34430 and the
commit that address them (commit 382b7afbe253) uses the old WM_STATE.
I am looking at this because I'm trying to fix QTBUG-57882 which is about
the l
Hi,
Is it possible that the failure (below) finding the QPA plugin in the test
set-up below is a result of this proposed change, somehow?
Or am I overlooking an error in the env. settings to load the required binaries
from the testing location?
Qt5 5.8.0RC built with the patch from https://code
Hello,
On Friday, 20 January 2017 15:06:53 CET Thiago Macieira wrote:
> On sexta-feira, 20 de janeiro de 2017 14:55:00 PST Sean Harmer wrote:
> > Just a query about the coding convention around inclusion of private
> > headers as specified at:
> >
> > https://wiki.qt.io/Coding_Conventions#Includi
On Mon, Jan 23, 2017 at 9:56 AM, René J.V. Bertin wrote:
> The error:
> %> env LD_LIBRARY_PATH=/opt/local/testing/libexec/qt5/lib
> QT_PLUGIN_PATH=/opt/local/testing/share/qt5/plugins
> QT_QPA_PLATFORM_PLUGIN_PATH=/opt/local/testing/share/qt5/plugins/platforms
> systray-qt5/systray-qt5
> This a
Il 21/01/2017 15:02, Иван Комиссаров ha scritto:
> Do I understand correctly that all is needed is to scan header of the
> texture, get some info from it and than load whole texture to the byte
> array?
Yes, get some metadata from the file, and no, not necessarily extract
the images as byte arrays
On Monday January 23 2017 10:30:50 Sérgio Martins wrote:
>Try running with QT_DEBUG_PLUGINS=1 and report back.
Hah, I think I was onto something, but it's not what I thought:
%> objdump -p systray-qt5/systray-qt5 | fgrep PATH
RPATH/opt/local/libexec/qt5/lib
As a result, all 5
Hi all,
Qt 5.8.0 and Qt Creator 4.2.1 releases are out! For details please see the blog
post (http://blog.qt.io/blog/2017/01/23/qt-5-8-released/,
http://blog.qt.io/blog/2017/01/23/qt-creator-4-2-1-released/) & visit in
https://www.qt.io/qt5-8/
Big thanks to everyone involved!
Br,
Jani
__
On segunda-feira, 23 de janeiro de 2017 11:00:02 PST Kevin Ottens wrote:
> > You need to be careful when including a private header from another
> > private
> > header. But if it's from a .cpp, you can use even relative paths.
>
> What do you have in mind as risk when you say one needs to be caref
2017.01.23 13:28, List for announcements regarding Qt releases and development
wrote:
Hi all,
1> Qt 5.8.0 and Qt Creator 4.2.1 releases are out!
Will there be a 5.7.2 release? Thanks.
___
Development mailing list
Development@qt-project.org
http://li
On segunda-feira, 23 de janeiro de 2017 19:13:17 PST Vincas Dargis wrote:
> 2017.01.23 13:28, List for announcements regarding Qt releases and
development wrote:
> > Hi all,
>
> 1> Qt 5.8.0 and Qt Creator 4.2.1 releases are out!
>
> Will there be a 5.7.2 release? Thanks.
No. There will be a 5.6
10 matches
Mail list logo