Hello Frank!
My ex-colleagues asked me to help port qt4.7/qwt5 based app to qt5/qwt6.1 and I
faced some problems. Some of them not fully solved yet.
Some issues were connected with deprecated methods in qt 5 (like
QString::toAscii) that I've used in my app, some issues were about missing
(renam
It wasn't hard at all. Most of it ran without modification. As long as you
have the line added to the PRO file that adds widgets, everything will
probably go easy.
So if you add that line in the pro file and then try compiling it. You'll
know soon enough ;-)
Dean
In a message dated 3/
I really didn't have any problems that I can remember. I had a bigger issue
in my own code making the conversions from Qt4 to Qt5. Just make sure that
you have
greaterThan(QT_MAJOR_VERSION, 4): QT += widget
in your *.pro file. That will allow you to still compile under Qt4. There
are a f
Hello Sergey!
On Sun, Mar 24, 2013 at 4:31 PM, Sergey Popov wrote:
> Hello Frank!
>
> My ex-colleagues asked me to help port qt4.7/qwt5 based app to qt5/qwt6.1 and
> I faced some problems. Some of them not fully solved yet.
> Some issues were connected with deprecated methods in qt 5 (like
> QS
On sábado, 23 de março de 2013 17.56.18, Uwe Rathmann wrote:
> > And will have definitely surpassed the old QWS
> > server when the input method mechanism is integrated into Wayland in the
> > next feature release.
>
> What we have is a touch, a couple of hard keys ( mapped to buttons ) and
> an en
On Sat, 23 Mar 2013 09:25:11 -0700, Thiago Macieira wrote:
> You may have heard stories about Wayland and whether it's ready for
> desktop usage. That's irrelevant... it's ready for embedded use already
> and has been for a year.
I have to make a platform decision ( unrelated to Qwt ) in the fol
On sábado, 23 de março de 2013 15.02.03, Uwe Rathmann wrote:
> > There is no QWS in Qt 5. It's replaced with QPA.
>
> But when comparing QPA/5.0 with QWS/4.8, what does it mean in terms of
> improvement/regression for a user today ?
I think the most important two differences are:
- QPA supports
>> I'm not using X11 at the moment, so it doesn't matter much to me,
>> but this sounds like a significant issue.
>
> Note that you will *not* see that regression if you're coming from Qt
> 4.8. The raster engine is the default in 4.8 already. The native engine
> was default in 4.7 and before.
Hm
On sexta-feira, 22 de março de 2013 11.39.16, K. Frank wrote:
> On Fri, Mar 22, 2013 at 10:34 AM, Uwe Rathmann
wrote:
> > On 03/21/2013 11:49 PM, K. Frank wrote:
> >> I am considering upgrading to Qt 5 (from Qt 4), but I also use qwt, and I
> >> am wondering whether I should expect any significant
Hi Uwe!
Thank you for the detailed reply.
On Fri, Mar 22, 2013 at 10:34 AM, Uwe Rathmann wrote:
> On 03/21/2013 11:49 PM, K. Frank wrote:
>
>> I am considering upgrading to Qt 5 (from Qt 4), but I also use qwt, and I am
>> wondering whether I should expect any significant issues doing so.
>
> On
Hello Dean!
On Thu, Mar 21, 2013 at 10:06 PM, wrote:
> It wasn't hard at all. Most of it ran without modification. As long as you
> have the line added to the PRO file that adds widgets, everything will
> probably go easy.
>
> So if you add that line in the pro file and then try compiling it. Yo
Hi Dean!
On Thu, Mar 21, 2013 at 8:10 PM, wrote:
> I really didn't have any problems that I can remember.
Thanks for the feedback.
> I had a bigger issue
> in my own code making the conversions from Qt4 to Qt5. Just make sure that
> you have
>
> greaterThan(QT_MAJOR_VERSION, 4): QT += widget
>
>
Hello Lists!
I am considering upgrading to Qt 5 (from Qt 4), but I also use qwt, and I am
wondering whether I should expect any significant issues doing so.
(As I've outlined in some related posts, I am considering upgrading the
compiler and various libraries I use, in part with an eye on using c
13 matches
Mail list logo
