Re: [Development] Using private API for qt-based library

2017-09-26 Thread Thiago Macieira 
On terça-feira, 26 de setembro de 2017 09:28:25 PDT Fabrice Salvaire wrote:
> Le 25/09/2017 à 10:56, Viktor Engelmann a écrit :
> > On 25.09.2017 10:29, iman ahmadvand wrote:
> >> Hi every one.
> >> I'm developing a set of specialized opensource widgets in c++ (called
> >> MaterialWidgets which is google material design implementation)
> >> Now i want to use private API for this library to prevent re
> >> implementing a bunch of logics behind those widgets.
> >> 
> >> What is your suggestion ?
> > 
> > don't
> 
> Sure, but in some particular cases, we have no choice when Qt don't
> expose the API

You do have a choice. Multiple, even. The first and simplest: don't do what 
you're trying to do.

Second, you can also add public API to allow what you're asking. See my other 
email sent to the interest mailing list.

The third option is to import the code you're developing into Qt. Then you are 
allowed to use the private API.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Using private API for qt-based library

2017-09-26 Thread Fabrice Salvaire 

Le 25/09/2017 à 10:56, Viktor Engelmann a écrit :


On 25.09.2017 10:29, iman ahmadvand wrote:

Hi every one.
I'm developing a set of specialized opensource widgets in c++ (called 
MaterialWidgets which is google material design implementation)
Now i want to use private API for this library to prevent re 
implementing a bunch of logics behind those widgets.


What is your suggestion ?

don't


Sure, but in some particular cases, we have no choice when Qt don't 
expose the API



As this lib depends on Qt, is it a bad idea to use private parts ?
Do you have other good design practice for me ?

For a showcase 
 i 
need to access 
QAbstractScrollAreaPrivate::scrollBarContainers->layout and remove 
scrollbars fromQAbstractScrollArea::viewport in my implementation.

Regards.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


--

Viktor Engelmann
Software Engineer

The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin
viktor.engelm...@qt.io
+49 151 26784521
http://qt.io

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B

The Future is Written with Qt
www.qtworldsummit.com


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development



___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] New approach to hi-dpi and coordinate system for layouts in Qt 6

2017-09-26 Thread Jason H 
> > The approaches available currently either
> > 
> > 1) scale everything after rendering (eg with SetProcessDPIAware())
> > 2) scale coordinates to screen metrics before rendering 
> > (QApplication::setAttribute(Qt::AA_EnableHighDpiScaling))
> > 
> > The first approach gives a blurry result because of up/down scaling and is 
> > not satisfying.
> > 
> > The second approach scales all coordinates, making it impossible to specify 
> > 'a one/two pixel border' without 
> > that getting scaled too. Additionally, the AA_EnableHighDpiScaling will 
> > only apply integer scaling, so on a 
> > screen with 150% scaling, the widget is scaled to 200%.  
> 
> I had a request to explain the problem with screenshots, so I created 
> 
>  https://bugreports.qt.io/browse/QTBUG-63402
> 
> with screenshots showing the previously posted code with the available 
> approaches and APIs to solving
> the problem, along with a screenshot showing the result of this proposal.

My crazy thought of the day:
The HTML 5 Canvas blits text 0.5 pixels offset. How would that change the top 
150% render?
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] MAINTAINERS: your action needed

2017-09-26 Thread Jani Heikkinen 
Hi all,

Quite many of these are still not in, see 
https://codereview.qt-project.org/#/q/message:%22Add+changes+file+for+Qt+5.9.2%22,n,z

Please finalize and get +2 as soon as possible; preferably already today. We 
need to get these in now to be able to get release out

br,
Jani

From: Development  on 
behalf of Jani Heikkinen 
Sent: Friday, September 22, 2017 12:34 PM
To: development@qt-project.org
Subject: [Development] MAINTAINERS: your action needed

Hi,

We did initial change files for Qt 5.9.2, see 
https://codereview.qt-project.org/#/q/message:%22Add+changes+file+for+Qt+5.9.2%22,n,z

Maintainers: Please do needed modifications immediately and get '+2' . We need 
these to be able to proceed with Qt 5.9.2 release

br,
Jani



___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt iOS - Customization of EditMenu

2017-09-26 Thread coroberti . 
Hi,
iOS developers are able to customize EditMenu (the one used to Select,
Select All, Copy, Cut, Paste, Speak, etc.)
using clear Apple's API.

Once I've used the approach recommended by Richard Moe Gustavsen:
https://bugreports.qt.io/browse/QTBUG-41275
that uses private API and is not working since Qt 5.5

Since that I cannot get rid from the standard items, for example, or
provide my custom actions on selecting them.

There is more mess related:
https://bugreports.qt.io/browse/QTBUG-49426

Any clues or directions or the maintainer would like this to be filed
as a feature request?

Thank you in advance!

Kind regards,
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development