Hi,
I have a documentation for my projects created with qdoc. Since I am using Qt
stuff here and there I link them in my docs:
e.g. \l QVariant
To make it work in the qdocconf (as per manual) I have:
indexes = $QT_INSTALL_DOCS/qtcore/qtcore.index
This seems to produce links to the Qt *on
Hello Everybody,
Along the same lines of a question I have asked in the past, as a rule of
thumb I never have a singleton hold a QWidget/QDialog from the instance of
a singleton. However I am not sure why I follow this basic principle. Does
anybody object to having the instance of a singleton be
On Wed, Aug 29, 2018 at 06:27:57PM +0200, Jason H wrote:
> It might be a minor point, but I think it would be good to have more uniform
> kit name structure.
This has irked me for a while, too.
>
> I'd like it to be Qt / Version / Platform like Qt 5.10.1 for Desktop Qt
> 5.10.1 for iOS Qt 5.10
+1
> On Aug 29, 2018, at 10:31 AM, Artem Sidyakin wrote:
>
> As a perfectionist with OCD myself :) I find this point to be more than minor
> as it has been bothering me for quite a some time now.
>
> ---
> Artem Sidyakin
>
>> On 29 Aug 2018, at 09:27, Jason H wrote:
>>
>> It might be a mino
As a perfectionist with OCD myself :) I find this point to be more than minor
as it has been bothering me for quite a some time now.
---
Artem Sidyakin
> On 29 Aug 2018, at 09:27, Jason H wrote:
>
> It might be a minor point, but I think it would be good to have more uniform
> kit name struct
Sure, I used this one:
https://github.com/retifrav/qml-webchannel-websockets/tree/master/websockets-mostly-qml/websockets
And here’s an article about that just in case:
https://retifrav.github.io/blog/2018/07/14/html-from-qml-over-webchannel-websockets/#mostly-qml
---
Artem Sidyakin
> On 27 Aug
