> Another question is what to do with the bundled libraries?
The -qt-xcb switch is there to reduce run-time dependencies. There always will
be somebody who wants
to run the latest Qt version on some old linux distribution.
Also I think it was decided that in Qt5 we can remove support for
Why can they be ignored?
I mean, we use only some of the API from that library, but bundle all of it. If
it is not fully covered by tests it is not an issue.
From: Hausmann Simon
Sent: Thursday, February 19, 2015 4:51 PM
To: Paeglis Gatis; Sébastien Fricker
Many of those files are from 3rdparty code, the ones I recognize are from
/qtbase/src/3rdparty/xkbcommon, those I think can
be ignored when thinking from code coverage point of view.
From: development-bounces+gatis.paeglis=theqtcompany@qt-project.org
Hi,
The idea is to move the compose file reading code out of Qt. libxkbcommon 5.0
(released on 2014-10-18 [1]) added support
for the compose keys. I did look at the new API already in October [2]. It
should be simple enough to remove the table generation code and use xkbcommon's
API instead. I
I would not be terribly upset if somebody that actually did work on the xcb
plugin stepped up and took this one :)
I would not say that I know all parts of the XCB plugin (yet), but I guess I
feel comfortable enough to be the default
assignee if nobody else is volunteering.
Gatis.
The latest change in that area was
https://codereview.qt-project.org/#change,79342 , it requires re-configuring Qt.
Did you do that? Also when using the bundled version of libkxbcommon, make sure
that in config.summary you
get:
xkbcommon .. yes (bundled copy, xkb-config-root
Regarding the xkbcommon, we are bundling 0.2.0, not 0.3.1.
I am waiting for the next release of xkbcommon, which will provide few new
functions that I want
to use in the xcb platform plugin. That is when I am planning to update the
bundled version as well.
Gatis.
Its probably because of the issue described in:
https://bugreports.qt-project.org/browse/QTBUG-30911
https://bugs.freedesktop.org/show_bug.cgi?id=23202
Switching between layouts should work in all cases, but adding a new layout
might not be seen until the application is restarted.
Did you set the environmental variable to QT_IM_MODULE=ibus?
From: development-bounces+gatis.paeglis=digia@qt-project.org
[development-bounces+gatis.paeglis=digia@qt-project.org] on behalf of
Yuchen Deng [loa...@gmail.com]
Sent: Saturday, May 11, 2013
: Saturday, May 11, 2013 4:18 PM
To: Paeglis Gatis
Cc: development
Subject: Re: [Development] Why I can't use ibus Input Method for type Chinese
character?
2013/5/11 Paeglis Gatis
gatis.paeg...@digia.commailto:gatis.paeg...@digia.com
QT_IM_MODULE=ibus
I did not set this environment variable. and I
It is a leftover, I have submitted a change:
https://codereview.qt-project.org/#change,52599
From: development-bounces+gatis.paeglis=digia@qt-project.org
[development-bounces+gatis.paeglis=digia@qt-project.org] on behalf of
Thiago Macieira
After looking at Qt4 / Qt5 source code and doing some internet search I see
that ibus plugin has become a part of Qt, where in Qt4 it was a separate plugin
hosted somewhere else..
Qt4 offered two options XIM and IBUS, selectable by using 'qtconfig' tool,
currently Qt5 has support only for
12 matches
Mail list logo
