Hi everyone!
I would like to ask your help in some Qt 5 matter. I think it's somewhat
related to QTBUG-31451, but not sure.
When I create a QGLWidget with a parent which not yet visible, then it
seems to fail to compile shaders although QGLContext is valid( at least the
isValid function returns t
Hi,
Could you please have a look at
https://bugreports.qt-project.org/browse/QTBUG-35168, I hope it could be
fixed in the final release. Thanks.
On Thu, Nov 28, 2013 at 6:18 PM, Heikkinen Jani wrote:
> Hi all,
>
>
>
> Qt 5.2 RC1 is coming really soon (hoping tomorrow) so please make sure all
>
On Nov 28, 2013, at 2:36 PM, Heikkinen Jani wrote:
> Hi all,
>
> We have finally Qt 5.2 RC1 candidate packages available in
> http://download.qt-project.org/snapshots/qt/5.2/5.2.0-rc1/2013-11-28_179/ .
> Mirroring is ongoing so it is possible that all packages aren’t visible yet
> but will
On Nov 28, 2013, at 12:53 PM, Adam Strzelecki wrote:
>> There are other installers though, either from Digia, or other companies
>> (enterprise Qt packages, SailfishOS SDK, …) which have other requirements.
>> Meaning that we need to have some kind of Qt installers for Mac anyhow.
>
> Agreed.
Hi all,
We have finally Qt 5.2 RC1 candidate packages available in
http://download.qt-project.org/snapshots/qt/5.2/5.2.0-rc1/2013-11-28_179/ .
Mirroring is ongoing so it is possible that all packages aren't visible yet but
will be soon ...
These packages will be RC1 packages if there isn't any
> Good ideas are welcome
>
(1) If you want it system wide, we could use well-known path relative to the
.app, either SDKs inside the .app itself, or „Qt" folder next to "Qt
Creator.app", I don’t know which one is better, but I believe /Applications
folder is best place because it easy to figure
On 27 Nov 2013, at 16:24, Ziller Eike wrote:
>
>>> Adding plugins into the respective frameworks would simplify deployment
>>> significantly. macdeployqt's task would be reduced to inspecting the
>>> frameworks the app links against, and copying the framework folders into
>>> the bundle. Don't
On 27 Nov 2013, at 12:06, Adam Strzelecki wrote:
>
> I am hereby submitting my candidature. I am registered Mac&iOS developer. I
> am personally interested to improve Qt experience on Mac, since I am using it
> for several projects. I may either submit patches or fork Git master.
>
> Of course
> There are other installers though, either from Digia, or other companies
> (enterprise Qt packages, SailfishOS SDK, …) which have other requirements.
> Meaning that we need to have some kind of Qt installers for Mac anyhow.
Agreed. If you have dedicated machine for dedicated tools that works b
Hi all,
Qt 5.2 RC1 is coming really soon (hoping tomorrow) so please make sure all
important known issues is listed in known issues wiki:
http://qt-project.org/wiki/Qt520-RC1-KnownIssues
Br,
Jani
___
Development mailing list
Development@qt-project.or
On Nov 27, 2013, at 9:28 PM, Adam Strzelecki wrote:
>> So that would always contain the Qt sources, documentation and examples too?
>
> Yes, Kai wrote he sees no point to be able to not install docs & examples
> together with SDK as suggested in QTBUG-34870. So once Qt Creator isn’t
> there,
On Nov 27, 2013 9:29 PM, "Adam Strzelecki" wrote:
> Correct me if I am wrong but there’s single ~/.config/…/QtCreator file,
so even we have several QtCreators all of them gonna see some SDK
registered by the other.
Several users can share one installation of Qt creator. We also support one
user h
12 matches
Mail list logo
