On Feb 19, 2016, at 10:58 PM, Andreas Holzammer
mailto:andreas.holzam...@kdab.com>> wrote:
Hi,
What about support for Windows IoT, which might be the successor of WEC.
Are there plans to support this?
Isn't this implicitly covered under Universal Windows Platform (Windows 10 +
WinRT APIs)?
T
>
> > Andreas Holzammer kirjoitti 20.2.2016
> kello 8.58:
> >
> > Hi,
> >
> > What about support for Windows IoT, which might be the successor of
> WEC.
> > Are there plans to support this?
> >
>
> We already have support for Windows 10 / WinRT, so it is a rather
> straightforward task to do whe
> Joseph Crowell kirjoitti 20.2.2016 kello 9.09:
>
> What about VS 2013?
>
Based on our understanding it offers quite decent C++11 support and should stay
supported.
Yours,
Tuukka
>> On 20/02/2016 7:01 AM, Knoll Lars wrote:
>> Hi,
>>
>> Now that 5.7 is branched, I'd like to propose that
> Andreas Holzammer kirjoitti 20.2.2016 kello 8.58:
>
> Hi,
>
> What about support for Windows IoT, which might be the successor of WEC.
> Are there plans to support this?
>
We already have support for Windows 10 / WinRT, so it is a rather
straightforward task to do when there is need. Maur
What about VS 2013?
On 20/02/2016 7:01 AM, Knoll Lars wrote:
Hi,
Now that 5.7 is branched, I'd like to propose that we update our list of
supported compilers and platforms for Qt 5.8. After some discussions with
different people, here's an initial proposal from my side:
* We drop support for
Hi,
What about support for Windows IoT, which might be the successor of WEC.
Are there plans to support this?
Thank you
Andy
Am 19.02.2016 um 22:01 schrieb Knoll Lars:
> Hi,
>
> Now that 5.7 is branched, I'd like to propose that we update our list of
> supported compilers and platforms for Qt
Hi,
Now that 5.7 is branched, I'd like to propose that we update our list of
supported compilers and platforms for Qt 5.8. After some discussions with
different people, here's an initial proposal from my side:
* We drop support for VS2012. This implicitly drops support for WEC2013. Reason
is t
Am 19.02.16 um 18:27 schrieb Welbourne Edward:
>> The user should choose the text size,
> Indeed - ideally as a device setup action that configures a
> device-global parameter that all apps get to work with. All font sizes
> should be specified in terms of the user-selected "comfortable size to
>
Shawn said:
> So maybe the best way to design the visual aspect of most applications
> is to use font-based units (like the em space) for physical sizes, but
> for touch UIs, to also use physical measurements as a minimum.
> e.g. width: Math.max(7mm, 3em) - will it be possible, or can we have
> nic
> On 19 Feb 2016, at 10:44, Gunnar Sletta wrote:
>
>
> One obvious usecase which always comes back to haunt is when those logical
> units need to be translated to actual pixels, such as when dealing with
> graphics. Up until some time ago, Something::size() was enough to decide the
> pixel d
> On 18 Feb 2016, at 11:50, Hausmann Simon
> wrote:
>
> Hi,
>
> A little while ago Lars and I proposed to introduce physical units in the QML
> language for use in QtQuick. The idea was to make it easier to write user
> interfaces that adapt to different display resolutions by "pinning" your
> On 18 Feb 2016, at 15:24, Welbourne Edward
> wrote:
>
> To meet all the actual use cases, we need three different *kinds* of
> size for things:
> * fraction of the available display area - good for top-level
>sub-division of the space an app has at its disposal to work in;
> * physical
Hi all,
We are planning to release Qt 5.6.0 RC really soon, hoping at the beginning of
next week. Final is targeted to be released within 2 weeks as well so we need
to get all change files done & in before it. Following change files are still
missing:
qtandroidextras
qtbase (ongoing, see ht
> On 18 Feb 2016, at 13:05, Sorvig Morten
> wrote:
>
>>
>> On 18 Feb 2016, at 12:35, Nikita Krupenko wrote:
>>
>> 2016-02-18 12:50 GMT+02:00 Hausmann Simon :
>>> (1) In order to make it really easy to scale "logical" pixels without
>>> having to introduce your own context property or factor
2016-02-19 0:08 GMT+02:00 Dominik Haumann :
> Interestingly, I once wrote a Value class [1] that does exactly this.
> It allows to have
> constructs like this:
>
> Value v1(2, Unit::Centimeter);
> Value v2 = Value::fromString("1in)"; // see also: toString()
> Value v3 = v1 * v2; // Restult is 4.45
15 matches
Mail list logo
