[Interest] Qt 5.6.0 on iOS - QGeoPositionInfoSource issues

Hi there, I run an interesting little project that provides an application across quite a few different OSs - with a Qt/QWidget UI for Windows, Mac, and various Linux flavors, and a QML UI (with currently significantly limited functionality) that can be built for Mac and Linux, but that is mai

[Interest] Crowdfunding campaign for QtWebEngine support in qutebrowser, a vim-like browser

Hi! (first of all, I hope this kind of thing is okay on this list - I decided to go for it after I saw some release announcements too. Please let me know if not, and sorry!) I'm the main developer of qutebrowser, a keyboard-focused vim-like web browser built using Qt and Python: http://www.qutebr

Re: [Interest] Amharic character support?

Awesome, thanks for the link. FYI: To use: main.cpp: QFontDatabase::addApplicationFont(":/assets/NotoSansEthiopic-Regular.ttf"); MyText.qml: Text{ family: "Montserrat,Noto Sans Ethiopic" } > Sent: Thursday, March 24, 2016 at 3:14 PM > From: "Jesse Jaara" > To: interest@qt-project.org > Subject:

Re: [Interest] Amharic character support?

24.03.2016, 20:44, Jason H kirjoitti: I'm not sure at all. I'm using Monserrat, which is a google font, which works for every language I have except that one. But somehow my browser can display it. I copied the text out of chrome and plopped it in. Actually the Montserrat font from google only

Re: [Interest] Amharic character support?

> On quinta-feira, 24 de março de 2016 17:41:30 PDT Jason H wrote: > > Amharic (Ethiopian) is giving me some trouble. All the other languages are > > fine. What do I need to do get Amharic characters showing? They are > > rendered as boxes. > > How are you sure you have a font with those characte

Re: [Interest] Ensuring that a queued invocation occurs after deferred deletion

> I've fixed it with the GameReference class. It seems an overkill to use a number of QObject instances to track a simple integer, but I'm glad it's working at least. Sorry I couldn't be of more help, but no one had been kind of enough to pitch in and put me out of my misery. :D Kind regards. O

[Interest] Qml Loader initial property setter

Hi, I was wondering if I am the only one who found the initial property of a source based Loader Item a bit annoying. inline sourceComponent with Component {} declaration are well ok on the other hand. I'm explaining myself, when using a loader you have 2 choice to set the initial binding on creat

Re: [Interest] Ensuring that a queued invocation occurs after deferred deletion

I've fixed it with the GameReference class. From: Nye Sent: Thursday, 24 March 2016 18:28 To: Curtis Mitch Cc: interest@qt-project.org Subject: Re: [Interest] Ensuring that a queued invocation occurs after deferred deletion > I've explained the problems with re

Re: [Interest] Ensuring that a queued invocation occurs after deferred deletion

> I've explained the problems with referencing the game object in the bug report. :) That's why I moved player.destroy(); out of the if (state == "invalid") block. But my last comment applies: unless there's a way to track explicitly the objects' lifetimes in QML I don't see how you can fix this.

Re: [Interest] Amharic character support?

On quinta-feira, 24 de março de 2016 17:41:30 PDT Jason H wrote: > Amharic (Ethiopian) is giving me some trouble. All the other languages are > fine. What do I need to do get Amharic characters showing? They are > rendered as boxes. How are you sure you have a font with those characters? Are you

Re: [Interest] Ensuring that a queued invocation occurs after deferred deletion

I've explained the problems with referencing the game object in the bug report. :) From: Nye Sent: Thursday, 24 March 2016 17:45 To: Curtis Mitch Cc: interest@qt-project.org Subject: Re: [Interest] Ensuring that a queued invocation occurs after deferred deletio

Re: [Interest] Ensuring that a queued invocation occurs after deferred deletion

Skimming through the source however, I'm not quite sure I reasoned correctly in my previous mail, as it seems the Loader will just change its status without tracking its children's lifetimes. So basically, Loader.Null is set immediately when it is made inactive. Sadly, I have neither more suggestio

Re: [Interest] Ensuring that a queued invocation occurs after deferred deletion

> The "loadedComponents" thing is more or less the same as the GameScope thing (I ended up calling it GameReference), except you need to remember to increment the count yourself, whereas with GameScope, it does it automatically. Mostly yes, except that this is tied to the loader, not to the loaded

[Interest] Amharic character support?

Amharic (Ethiopian) is giving me some trouble. All the other languages are fine. What do I need to do get Amharic characters showing? They are rendered as boxes. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listi

Re: [Interest] Canvas keeping artifacts

reverse engineering of methods on object, we have some debug tools to list methods and properties on object at run time, kinda what KDAB Gamma Ray is doing https://www.kdab.com/gammaray/ So I try it out, I remembered having a hard time with the same problems. The rest are probably left over from pr

Re: [Interest] Canvas keeping artifacts

By the way, reset() is not a W3C function, and it's also not in the QML Canvas documentation.   I'm wondering how you found it?       Sent: Thursday, March 24, 2016 at 9:42 AM From: "Jason H" To: "Jérôme Godbout" Cc: "interest@qt-project.org Interest" Subject: Re: [Interest] Canvas keepin

Re: [Interest] Canvas keeping artifacts

ctx.reset(); fixes it.   Again, I think you have meaningless statements. ctx.beginPath(); // It's not a path ctx.fillStyle = 'rgba(0,0,0,0)'; // it's not using fillStyle ctx.clearRect(0,0,width,height); // this works ctx.fill(); // there is no closed path to fill   Sent: Wednesday, Mar

Re: [Interest] [Quick] GridView inside the Layout

> "The implicit size of the GroupBox > is calculated > based on the size of its content. If you want to anchor items inside the > group box, you must specify an explicit width and height on the GroupBox >

Re: [Interest] Ensuring that a queued invocation occurs after deferred deletion

The "loadedComponents" thing is more or less the same as the GameScope thing (I ended up calling it GameReference), except you need to remember to increment the count yourself, whereas with GameScope, it does it automatically. The problem with the code you posted is as I mentioned earlier: Load

[Interest] Calendar widget style sheet

All, I have a touch screen project with a 600 pixel width and 1024 height. On one of the pages we need a calendar widget but we need it to look good and be "finger sized". I poked around quite a bit and found a starter stylesheet on this thread: http://www.qtcentre.org/threads/30478-How-To-Ch

Re: [Interest] Ensuring that a queued invocation occurs after deferred deletion

"Supposedly setting the source of the loader to NULL" to be read as "Supposedly setting the source of the loader to an empty string" On Thu, Mar 24, 2016 at 12:25 PM, Nye wrote: > Okay, > It might sound stupid, but why not notify the game from your loaders? > Supposedly setting the source of the

Re: [Interest] Ensuring that a queued invocation occurs after deferred deletion

Okay, It might sound stupid, but why not notify the game from your loaders? Supposedly setting the source of the loader to NULL will unload the component (at least that's what the documentation says). Something like this (please bear with my tortured QML knowledge): Item { id: theGame pr

Re: [Interest] [Quick] GridView inside the Layout

"The implicit size of the GroupBox is calculated based on the size of its content. If you want to anchor items inside the group box, you must specify an explicit width and height on the GroupBox

Re: [Interest] Ensuring that a queued invocation occurs after deferred deletion

The problem with doing this is that you'd still need to identify the Loaders that are relevant to (have references to) the game, so you'd end up with more or less the same amount of extra QML code (a line or two). It also ties it to Loaders, but the same problem exists with the destroy() JavaScr

[Interest] [Quick] GridView inside the Layout

I guess my assumption about qt-quick Layouts might not be right. Consider a window where there are some properties, but they all inside a `ColumnLayout` so that `ScrollView` would be able to use on it. Also there is some QtQuick.Controls inside them. I guess code would be more expository. import Q