On 10/13/21 11:58, Giuseppe D'Angelo via Development wrote:
On 13/10/2021 11:43, Albert Astals Cid via Development wrote:
Should we allow some small features outside of the declared SVG Tiny 1.2
support?
I'm not against in principle (liberal in what you accept, etc.etc.), but
as you say, it's
On 04/28/20 11:04, Kevin Kofler wrote:
QList and QVector should remain as they are in Qt 5.
But ... some developers are not able to understand the difference, so
we need to remove one class!!1!
___
Development mailing list
Development@qt-project.org
On 02/06/20 12:45, Lars Knoll wrote:
As a side note: SSE 4.1 offers some nice additional instructions that would
simplify some of the operations. Should we keep the minimum requirement for SSE
at version 2, or can we raise it to 4.1?
I have a classroom-sized deployment of Intel Centrino Duo b
On 12/04/19 12:56, Volker Hilsheimer wrote:
Hi,
QApplication::globalStrut is a property that has outlived its purpose.
IIRC, then I added that in the early Qt 2 days, anticipating that with
Qt/Embedded we might see our widgets landing on touch screens “any moment now”.
The idea was to have a
On 11.10.2017 08:56, Martin Koller wrote:
on openSuse 42.2 I have a self-built 5.9.1 version and also the openSuse 5.9.1
installed one.
For some reason (which is not important for my question) my application picks
up the openSuse library
but fails with the error
libQt5Core.so.5: version `Qt_5.9
On 08.07.2017 13:24, Massimo Callegari via Development wrote:
2) Security ? There is none.
If you deploy an application using a TextField control with echoMode:
TextInput.Password, one can easily add some trivial JavaScript code to the
comfortably reachable QtQuick/Controls.2/TextField.qml file
On 09.06.2017 17:17, Aveek Basu wrote:
This is Aveek from Linux Foundation. Currently myself and Till Kempeter,
are working as the org admins of the LF GSoC project. This year have
undertaken a project of developing the Common Print Dialog for Linux (
https://wiki.linuxfoundation.org/gsoc/google-
On 25.05.2017 19:03, André Somers wrote:
On 25 May 2017, at 18:40, Christoph Feck wrote:
On 25.05.2017 13:53, André Somers wrote:
Op 25/05/2017 om 12:38 schreef Konstantin Tokarev:
Other problem, that IMO is more serious, is that Qt *requires* user to use
QList,
by returning or taking it as
On 25.05.2017 13:53, André Somers wrote:
Op 25/05/2017 om 12:38 schreef Konstantin Tokarev:
Other problem, that IMO is more serious, is that Qt *requires* user to use
QList,
by returning or taking it as and argument in various places. That's almost only
reason why I use QList in my code[*].
If
On 31.01.2017 09:55, Michael Weghorn wrote:
[...] The links about the plans for the Qt print system that
John provided in his email [1] give some kind of overview, but are
currently not enough for me to deduce the concrete next steps that need
to be taken for the implementation.
If you (or some
On 05.01.2017 17:12, Edward Welbourne wrote:
Sérgio Martins very helpfully linked to KCalendarSystem - thank you.
One of the things we should clearly aim for is to make it easy for
KCalendarSystem to (when its developers care to and can find the time,
with no pressure to do so) adapt to use QCale
On 16.11.2016 17:22, Niccolò Belli wrote:
Hi Morten,
I'm sorry, I missed your reply.
RoundPreferFloor Round up for .75 and higher
RoundPreferFloor is the new default. Do you think this is sufficient?
qFloor would help for my monitor, of course.
Unfortunately the default (RoundPreferFloor)
On Wednesday 11 February 2015 17:23:51 Christoph Feck wrote:
> On Wednesday 11 February 2015 17:20:04 Guido Seifert wrote:
> > Minor OT, but I am too curious... do you have an example?
> > Are there really cases were turning lower case into upper case or
> > vice versa ch
On Wednesday 11 February 2015 17:20:04 Guido Seifert wrote:
> Minor OT, but I am too curious... do you have an example?
> Are there really cases were turning lower case into upper case or
> vice versa changes the length of a string?
office (4 code points) -> OFFICE (7 code points)
__
On Monday 10 November 2014 12:04:27 Stanislav Baiduzhyi wrote:
> Have anyone noticed that Qt5 subpixel font rendering is different
> from Qt4?
Yes, https://bugreports.qt-project.org/browse/QTBUG-40971
___
Development mailing list
Development@qt-project.o
. Unfortunately, this function is no longer
available in Qt5, so in a few years, we will see the same long
discussion as in https://bugs.kde.org/show_bug.cgi?id=165044
--
Christoph Feck
http://kdepepo.wordpress.com/
KDE Quality Team
___
Development
On Tuesday 16 September 2014 14:11:26 Knoll Lars wrote:
> In addition, we also now have a new company name for the Qt part of
> Digia. It’s simply ‘The Qt Company’.
How boring! But you can rename the company hundred times... For me, it
will always be The Trolls™ ;)
Christoph Feck (k
On Tuesday 22 April 2014 23:11:59 Kleint Friedemann wrote:
> Hi Christoph,
>
> > Christoph Feck wrote: Not speaking for Michael, but let me add
> > that C++ is much easier to debug compared to QML, if you get a
> > crash. We have nearly hundred backtraces in the Plasma bu
5, or 332646 to cite only some fairly recent ones.
I am not blaming QML here, all those bugs are possibly caused by
errors in Plasma itself, but the fact that you cannot see from the
backtrace what caused the crash is a major concern for me.
--
Christoph Feck
http://kdepepo.wordpress.com/
K
is implemented with QFtp. We're
> intending to migrate to Qt5 later this year but since QFtp is
> deprecated in Qt5 this functionality isn't possible.
Is https://qt.gitorious.org/qt/qtftp/source/readme.txt an option?
--
Christoph Feck
http://kdepepo.wordpress.com/
K
that
> foo(const char *).
>
>
> Anyone care? Where should I forward this email to?
>
> Thanks,
> Tony
You are right, but what is your actual question?
Christoph Feck (kdepepo)
KDE Quality Team
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
codecs will be
> unconditionally enabled
I have seen crashes ending in Qt SSE2 helper functions, probably
because they access more data than needed due to the SIMD nature of
the instructions. This can cause access violations on page boundaries.
Has the Qt SSE2 code been audited for avoi
t for larger
bit depths was rejected, but cannot find the reference right now (to
check how old the proposal was).
Christoph Feck (kdepepo)
KDE Quality Team
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
leaks.
>
> Best regards,
> Luka
Please use https://bugreports.qt-project.org/ to report issues.
--
Christoph Feck
http://kdepepo.wordpress.com/
KDE Quality Team
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On Wednesday 02 October 2013 00:41:56 Thiago Macieira wrote:
> On quarta-feira, 2 de outubro de 2013 00:04:58, Christoph Feck
wrote:
> > On Tuesday 01 October 2013 21:20:29 Thiago Macieira wrote:
> > > Should we disable exceptions in QtCore?
> >
> > If it allows
gt; Should we disable exceptions in QtCore?
If it allows us to get a backtrace actually showing where the
unhandled exception was thrown (instead of saying it was caused by the
Qt event loop), I am all for disabling exception support in QtCore.
--
Christoph Feck
http://kdepepo.wordpress.
On Monday 26 August 2013 14:39:50 Kurt Pattyn wrote:
> On 26 Aug 2013, at 14:26, Christoph Feck
wrote:
> > What do you mean with "maintained as is"? The document you cite
> > does not mention anything related to invalid UTF-8.
>
> Unicode strictly requires no
intained as is"? The document you cite does
not mention anything related to invalid UTF-8.
Since this is the Qt development list, please discuss code changes
needed to clarify what you mean.
--
Christoph Feck
http://kdepepo.wordpress.com/
KDE Quality Team
__
le it (as far
as I know, it refuses to do it in current versions).
To me this sounds much less work to adapt an application. What am I
missing?
Christoph Feck
http://kdepepo.wordpress.com/
KDE Quality Team
___
Development mailing list
Development@qt-pr
On Thursday 06 September 2012 00:53:37 Ariel Molina wrote:
> 5) Nobody cares about Wacom anyway
I do, every day. I reported bugs for Qt 4, until it worked correctly
on a Tablet PC, and expect me to do the same for Qt 5.
--
Christoph Feck
http://kdepepo.wordpress.com/
KDE Quality T
final result may be displayed at 8 bit precision, but internally Qt
needs more depth when it comes to correctly colored images).
Also, the new printing framework in Qt should use the new
QtColorManagement module, so some coordination with experts would be
needed.
--
Christoph Feck
http://kdepep
On Thursday 05 July 2012 14:08:45 Laszlo Papp wrote:
> Using eigen for managing some coordinates sounds utterly overkill.
Either you haven't looked at Eigen, or you haven't understood it.
Christoph Feck (kdepepo)
KDE Quality Team
__
On Monday 07 May 2012 15:03:29 Samuel Rødal wrote:
> On 05/04/2012 04:22 PM, ext Samuel Rødal wrote:
> > As for the open source drivers I don't know of any reliable way
> > of enabling vsync. There's the GLX_SGI_video_sync extension
> > which is supposed to give a uniform way to sync rendering
> >
On Friday 04 May 2012 13:37:04 Samuel Rødal wrote:
> Hello,
>
> to be able to achieve smooth animations in QML 2, the animations
> should ideally use a fixed timestep, and not a timer which might
> have inaccuracies depending on the platform and won't give fully
> smooth results.
Does OpenGL 2 ha
On Wednesday 11 April 2012 11:40:15 BogDan wrote:
> There is no QMenu::show, and this is the problem !:)
QMenu::show() calls QWidget::show(), which simply calls
QWidget::setVisible(true). And this one is virtual, case closed ;)
--
Christoph Feck
http://kdepepo.wordpress.com/
KDE Quality T
cluded into 5.0, the lower the frustation will be when it
is later discovered that they are ill-designed.
--
Christoph Feck
http://kdepepo.wordpress.com/
KDE Quality Team
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
age
(lets say 100x100 pixels) to pos (0, 0), then blitting rect
(0,0,100,100) to (0,100,100,100), then (0,0,200,100) to
(0,200,200,100) etc., effectively doubling the filled size with each
blit.
--
Christoph Feck
http://kdepepo.wordpress.com/
KD
ership, will be much appreciated by those
who plan to submit patches for those rusty areas ;)
--
Christoph Feck
http://kdepepo.wordpress.com/
KDE Quality Team
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/li
classes, such as QLineF, have functions that are used
outside rendering, so having double-precision classes are very useful
to have.
Maybe add explicit QRectS and QRectD classes, and deprecate QRectF
(same for QPointF, QLineF and friends)?
--
Christoph Feck
http://kdepepo
hands down.
As far as I remember, POSIX locales offer strings or regexps for YES
and NO, so it might be possible to add something to QLocale to access
those strings.
--
Christoph Feck
http://kdepepo.wordpress.com/
KDE Quality Team
___
Development ma
> Thanks,
> Keith
QImage supports 8 bit grayscale images via QImage::Format_Indexed8.
Depending on how you initialize the palette, you can have value 255
mean black or white.
Rendering to 8 bit images is not supported, though.
--
Christoph Feck
http://kdepep
41 matches
Mail list logo
