[Interest] QApplication.activeWindow().pos() not returning correct value after sacling on OSX

[Frank Rueter | OHUfx]

Hi,

I am trying to figure out my host application's window geometry reliably 
and am struggling a bit.


I use QApplication.activeWindow().geometry() to drive my custom widget's 
geometry (I need to sit exactly on top of the host application).
All works fine and my widget sits exactly on top of the host application 
window, until the host app is scaled by dragging one of it's sides out 
or in. After that QApplication.activeWindow().geometry() still returns 
the same exact position, though the size is correct, resulting in an 
offset for my widget.
Turns out scaling windows on OSX by dragging their edges doesn't seem to 
update QApplication.activeWindow().pos()


As soon as I grab the title bar and move the host app a tiny bit, 
QApplication.activeWindow().pos() seems to be updated correctly.


Is there a fix/workaround for this?

Cheers,
frank

--
ohufxLogo 50x50  	*vfx compositing 
 | *workflow customisation 
and consulting * *


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] qt.labs.controls and colors

[ekke]

Hi,

as I understand it right, I can define two colors for Material:

  * primary
  * accent

and one for Universal : accent.

At the moment I'm only focussing on Material.
to follow Android Material Design Guide I also need a darker and lighter
variation of primary
is it ok, to do it this way:

Qt.lighter(Material.accentColor, 1.1)
Qt.darker(Material.accentColor, 1.1)

as next I need some more colors:

  * primaryText and secondaryText (depends from light or dark theme)
  * textColorPrimary (textcolor used for text placed on primary color)


as from documentation there's nothing generated / prepared from Qt Material
so I have to create these colors by myself and then use thru the app ?

what's the best in respect of performance and memory ?
should I define these colors in my root qml as property and use this
property thru the app ?

color: root.secondaryTextColor

last question:
Is there a way to set the *Android Status Bar* color (Primary Dark) ?
http://developer.android.com/training/material/theme.html#StatusBar

thx
-- 

ekke (ekkehard gentz)

independent software architect
international development native mobile business apps
BlackBerry 10 | Qt Mobile (Android, iOS)
workshops - trainings - bootcamps

*BlackBerry Elite Developer
BlackBerry Platinum Enterprise Partner*

max-josefs-platz 30, D-83022 rosenheim, germany
mailto:e...@ekkes-corner.org
blog: http://ekkes-corner.org
apps and more: http://appbus.org

twitter: @ekkescorner
skype: ekkes-corner
LinkedIn: http://linkedin.com/in/ekkehard/
Steuer-Nr: 156/220/30931 FA Rosenheim, UST-ID: DE189929490

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Speeding up linking for iOS?

[Thiago Macieira]

On segunda-feira, 15 de fevereiro de 2016 15:22:24 PST Bob Hood wrote:
> On 2/15/2016 3:00 PM, Thiago Macieira wrote:
> > On segunda-feira, 15 de fevereiro de 2016 18:24:48 PST Jason H wrote:
> >> It takes forever for my app to link for iOS. Is there anyway to speed
> >> this
> >> up?
> > 
> > Upgrade to 5.7 and start using the shared library build of Qt for iOS.
> 
> 5.7?  Did I miss an entire release of Qt?  I only see 5.5 as the highest
> available in the official releases download.

No, you did not. Qt 5.6.0 is not yet released, but this feature is not 
available there.

And I was actually wrong: this is not in Qt 5.7. This will be present in 
Qt 5.8 only (it's not yet ready).

For more information, see
https://codereview.qt-project.org/123023

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

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Speeding up linking for iOS?

[Bob Hood]

On 2/15/2016 3:00 PM, Thiago Macieira wrote:

On segunda-feira, 15 de fevereiro de 2016 18:24:48 PST Jason H wrote:

It takes forever for my app to link for iOS. Is there anyway to speed this
up?

Upgrade to 5.7 and start using the shared library build of Qt for iOS.


5.7?  Did I miss an entire release of Qt?  I only see 5.5 as the highest 
available in the official releases download.


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Speeding up linking for iOS?

[Thiago Macieira]

On segunda-feira, 15 de fevereiro de 2016 18:24:48 PST Jason H wrote:
> It takes forever for my app to link for iOS. Is there anyway to speed this
> up?

Upgrade to 5.7 and start using the shared library build of Qt for iOS.

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

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QtWebEngine in 5.6 OSX 32 bit

[Allan Sandfeld Jensen]

On Monday 15 February 2016, Konstantin Tokarev wrote:
> 15.02.2016, 22:01, "Glenn Ramsey" :
> > On 16/02/16 00:01, Koehne Kai wrote:
> >>>  -Original Message-
> >>>  From: Interest [mailto:interest-boun...@qt-project.org] On Behalf Of
> >>> Glenn Ramsey
> >>>  Sent: Sunday, February 14, 2016 9:24 PM
> >>>  To: interest@qt-project.org
> >>>  Subject: [Interest] QtWebEngine in 5.6 OSX 32 bit
> >>> 
> >>>  Hi,
> >>> 
> >>>  In 5.6 is it still supposed to be possible to build QtWebEngine using
> >>> - platform
> >>>  macx-clang-32 ?
> >> 
> >>  No, it's not. Upstream Chromium/Chrome dropped support a while ago:
> > Thanks. This means that 5.5.1 shouldn't have been able to build with
> > macx-clang-32 either, but it does and seems to work Ok.
> 
> QtWebEngine in 5.5.1 used older Chromium version.
> 
Yes, but 5.5 still used Chromium 40, and supposedly Google removed official 
32-bit support for Mac in Chromium 39, but I guess it took a few versions 
before anything broke from the lack of deliberate support.

Regards
`Allan
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QtWebEngine in 5.6 OSX 32 bit

[Konstantin Tokarev]

15.02.2016, 22:01, "Glenn Ramsey" :
> On 16/02/16 00:01, Koehne Kai wrote:
>>>  -Original Message-
>>>  From: Interest [mailto:interest-boun...@qt-project.org] On Behalf Of Glenn
>>>  Ramsey
>>>  Sent: Sunday, February 14, 2016 9:24 PM
>>>  To: interest@qt-project.org
>>>  Subject: [Interest] QtWebEngine in 5.6 OSX 32 bit
>>>
>>>  Hi,
>>>
>>>  In 5.6 is it still supposed to be possible to build QtWebEngine using -
>>>  platform
>>>  macx-clang-32 ?
>>
>>  No, it's not. Upstream Chromium/Chrome dropped support a while ago:
>
> Thanks. This means that 5.5.1 shouldn't have been able to build with
> macx-clang-32 either, but it does and seems to work Ok.

QtWebEngine in 5.5.1 used older Chromium version.

>
>>  
>> http://googleappsupdates.blogspot.co.uk/2014/09/google-chrome-64-bit-for-mac-and-windows.html
>>
>>  We'll document this.
>
> Ideally the configure or build system should complain if you attempt to do it.
> That would save a lot of time.
>
> Glenn
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

-- 
Regards,
Konstantin
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QtWebEngine in 5.6 OSX 32 bit

[Glenn Ramsey]

On 16/02/16 00:01, Koehne Kai wrote:
> 
> 
>> -Original Message-
>> From: Interest [mailto:interest-boun...@qt-project.org] On Behalf Of Glenn
>> Ramsey
>> Sent: Sunday, February 14, 2016 9:24 PM
>> To: interest@qt-project.org
>> Subject: [Interest] QtWebEngine in 5.6 OSX 32 bit
>>
>> Hi,
>>
>> In 5.6 is it still supposed to be possible to build QtWebEngine using -
>> platform
>> macx-clang-32 ?
> 
> No, it's not. Upstream Chromium/Chrome dropped support a while ago:

Thanks. This means that 5.5.1 shouldn't have been able to build with
macx-clang-32 either, but it does and seems to work Ok.

> http://googleappsupdates.blogspot.co.uk/2014/09/google-chrome-64-bit-for-mac-and-windows.html
> 
> We'll document this.

Ideally the configure or build system should complain if you attempt to do it.
That would save a lot of time.

Glenn

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Speeding up linking for iOS?

[Jason H]

It takes forever for my app to link for iOS. Is there anyway to speed this up?

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] qt.labs.controls - gallery - scrolling gestures and StandardKeys not working from capazitive keyboard

[Nurmi J-P]

> On 14 Feb 2016, at 11:58, ekke  wrote:
> 
> before entering bug issues I wanted to ask if I'm doing something wrong or I 
> forgot to add something to the controls
> 
> Scrolling from Capazitive Keyboard
> tried with gallery example (ScrollBar) and own code
> 
> I'm using BlackBerry PRIV (Android 5.1.1) which is a slider where the 
> physical keyboard is a capazitive keyboard wher you can swipe and normally 
> android apps then are scrolling up/down in lists, large pages, webview and 
> more out of the box - per ex. from GMail app, PlayStore, Fotos, ...
> 
> there are two blogs describing HowTo deal with the keyboard from android 
> apps, where the second one describes the capazitive keyboard:
> http://devblog.blackberry.com/2015/11/ready-set-type-developers-guide-to-the-priv-keyboard-part-1/
>  
> http://devblog.blackberry.com/2015/11/ready-set-type-developers-guide-to-the-priv-keyboard-part-2/
> 
> perhaps I have to add more to the controls as ScrollBar{} ?
> tried to set focus: true - didn't help
> 
> the keyboard itself was correctly recognized by Qt 5.6:
> opening the slider - the virtual keyboard disappears and closing it reappears.
> 
> Shortcuts
> Shortcuts using strings are working :)
> sequence: "b"
> sequence: "alt+b"
> 
> StandardKey unfortunately is not working :(
> in other apps this is working, per ex. the Delete key is recognized and used 
> to delete something like an email

Sounds like worth opening bug reports. There we can dig into details. Thanks! :)

--
J-P Nurmi

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qt 5.6 and labs.controls for mobile development

[Nurmi J-P]

Hi,

> On 14 Feb 2016, at 19:56, ekke  wrote:
> 
> just before starting my blog articles about Qt 5.6 for mobile development 
> have some questions:
> 
> Mobile Development for Android, iOS (later W10)
> What's the best way to develop for more then one platform from one Qt Creator 
> Project ?
> read about QtFileSelectors and think they can help with .qml files and also 
> images:
> placing them in +android, +ios folders I should be able to use different icon 
> sets and do some fine-tuning in UI.
> For Android the Material styled controls are looking good.
> Using some iOS - specific icons will help to use Material for iOS apps.
> Am I right, that using file selectors this selection will happen at runtime ?

Yes, the selection happens at runtime.

> So always all kinds of resources will be deployed ?

Sharing and separating platform specific resources can be done by using 
platform scopes in the .pro file.

# resources that apply to all platforms
RESOURCES += myapp.qrc

# Android specific resources
android: RESOURCES += myapp_android.qrc

# iOS specific resources
ios: RESOURCES += myapp_ios.qrc

> And what about CPP code - what's the easiest way to manage different target 
> platforms like Android and iOS ?

You could use the Q_OS_* macros (eg. Q_OS_ANDROID) for smaller platform 
specific code blocks. If you have more complex platform specific features, it’s 
usually better to have separate source files (eg. myfeature_android.cpp) and 
use the same technique than shown above for resources.

> Thanks for all tips and hints - don't want to publish wrong recipes ;-)
> 
> Using different styling (Material vs Universal)
> the Qt 5.6 qt.labs.controls Gallery example does the switch at startup using 
> QT_LABS_CONTROLS_STYLE.
> This works for the qt.labs.controls
> But as soon as I'm customizing controls I have to...
> import Qt.labs.controls.material 1.0
> 
> color: Material.accentColor
> 
> so the customized controls have different code for Material and Universal
> HowTo deal with this ?
> Or should I restrict Universal to Windows ? Then I could use the 
> FileSelectors.

We’re working on adding the style names as built-in selectors, so in the future 
you could have MyPage.qml, +material/MyPage and +universal/MyPage.qml if you 
want to do more complex style specific tweaks.

--
J-P Nurmi

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QtWebEngine in 5.6 OSX 32 bit

[Koehne Kai]

> -Original Message-
> From: Interest [mailto:interest-boun...@qt-project.org] On Behalf Of Glenn
> Ramsey
> Sent: Sunday, February 14, 2016 9:24 PM
> To: interest@qt-project.org
> Subject: [Interest] QtWebEngine in 5.6 OSX 32 bit
> 
> Hi,
> 
> In 5.6 is it still supposed to be possible to build QtWebEngine using -
> platform
> macx-clang-32 ?

No, it's not. Upstream Chromium/Chrome dropped support a while ago:

http://googleappsupdates.blogspot.co.uk/2014/09/google-chrome-64-bit-for-mac-and-windows.html

We'll document this.

Regards

Kai 
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] qt.labs.controls Material Toasts

[Samuel Gaist]

Hi,

Ok, I see what you mean :)

I was asking because I've started some time ago to implement (early WIP) a 
pluggable notification system for Qt so I was wondering if it could benefit to 
these custom notifications.

If interested, you can take a look at 
https://codereview.qt-project.org/#/c/97068/

It's not ready yet but the more inputs the better :)

Samuel

On 12 févr. 2016, at 16:17, Nurmi J-P  wrote:

> Hi Samuel,
> 
> We’ll probably leave the native notification system integration job to the 
> platform extras or other modules. The new controls are built upon so called 
> Qt Quick templates, and the whole styling system is heavily based on Qt 
> Quick. They are all fully cross-platform styles implementing specific design 
> languages. They are not pretending to be native styles, because there’s 
> actually nothing native there. Bridging native controls doesn’t fit very well 
> into the picture of this project. If we wanted to go native, direct QML 
> bindings to native controls would be my preferred solution. It would be a 
> parallel offering, not mixed with Qt Quick. :)
> 
> --
> J-P Nurmi
> 
> 
> 
>> On 12 Feb 2016, at 13:50, Samuel Gaist  wrote:
>> 
>> Hi,
>> 
>> Out of curiosity, should that be driven by the OS notification system ?
>> 
>> Samuel
>> 
>> On 11 févr. 2016, at 16:45, Nurmi J-P  wrote:
>> 
>>> Hi,
>>> 
>>> We would definitely like to extend our offering with some sort of tooltips 
>>> and notification banners in the future. We might prefer stick to the 
>>> terminology Qt and Qt Quick have used in the past, so we probably won’t end 
>>> up calling them snackbars, toasts, or anything else as delicious, though. :)
>>> 
>>> I have filed suggestions for both so they don’t get forgotten:
>>> -  https://bugreports.qt.io/browse/QTBUG-51003
>>> -  https://bugreports.qt.io/browse/QTBUG-51060
>>> 
>>> --
>>> J-P Nurmi
>>> 
>>> From: Interest [mailto:interest-boun...@qt-project.org] On Behalf Of ekke
>>> Sent: Thursday, February 11, 2016 10:47
>>> To: interest@qt-project.org
>>> Subject: Re: [Interest] qt.labs.controls Material Toasts
>>> 
>>> sorry, was an old link - this one is the actual one:
>>> https://www.google.com/design/spec/components/snackbars-toasts.html
>>> 
>>> Am 11.02.16 um 10:39 schrieb ekke:
>>> Hi,
>>> 
>>> are there any plans to provide Snackbars and Toasts out of the box ?
>>> http://blog.chengyunfeng.com/design/spec/components/snackbars-and-toasts.html
>>> 
>>> or do I have to implement them by trying to customize existing controls ?
>>> 
>>> thx
>>> --
>>> ekke (ekkehard gentz)
>>> 
>>> independent software architect
>>> international development native mobile business apps
>>> BlackBerry 10 | Qt Mobile (Android, iOS)
>>> workshops - trainings - bootcamps
>>> 
>>> BlackBerry Elite Developer
>>> BlackBerry Platinum Enterprise Partner
>>> 
>>> max-josefs-platz 30, D-83022 rosenheim, germany
>>> mailto:e...@ekkes-corner.org
>>> blog: http://ekkes-corner.org
>>> apps and more: http://appbus.org
>>> 
>>> twitter: @ekkescorner
>>> skype: ekkes-corner
>>> LinkedIn: http://linkedin.com/in/ekkehard/
>>> Steuer-Nr: 156/220/30931 FA Rosenheim, UST-ID: DE189929490
>>> 
>>> 
>>> 
>>> ___
>>> Interest mailing list
>>> Interest@qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/interest
>>> 
>>> 
>>> --
>>> ekke (ekkehard gentz)
>>> 
>>> independent software architect
>>> international development native mobile business apps
>>> BlackBerry 10 | Qt Mobile (Android, iOS)
>>> workshops - trainings - bootcamps
>>> 
>>> BlackBerry Elite Developer
>>> BlackBerry Platinum Enterprise Partner
>>> 
>>> max-josefs-platz 30, D-83022 rosenheim, germany
>>> mailto:e...@ekkes-corner.org
>>> blog: http://ekkes-corner.org
>>> apps and more: http://appbus.org
>>> 
>>> twitter: @ekkescorner
>>> skype: ekkes-corner
>>> LinkedIn: http://linkedin.com/in/ekkehard/
>>> Steuer-Nr: 156/220/30931 FA Rosenheim, UST-ID: DE189929490
>>> ___
>>> Interest mailing list
>>> Interest@qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/interest
>> 
> 
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest