Eike:
Thank you for your response. I will be happy to ask the question on the
appropriate list, but I am not convinced that this is a Qt question. Here is
an explicit example.
The Qt API provides QSyle::standardIcon() to deal with exactly the case that
concerns me: fetching an appropriate icon for the current style from code
that is "style independent". The implementation of this icon construction
would be:
QApplication::style()->standardIcon(*QStyle::SP_DirOpenIcon*)
where *SP_DirOpenIcon* might be any valid enumeration value taken from
QStyle::StandardPixmap. So the API offers a clear mechanism to achieve what
I am after.
The puzzle is that QT Creator does not allow me to specify this kind of
"style dependent" icon. I would have expected this (naively) to be a third
case in the "icon source" drop-down (that is: "Choose File", "Choose
Resource", or "*Choose Styled Icon*"), or that there would be some way to
specify a resource name that would map to the "standard" resource set that
is available through QStyle. So it appears to me that the deficiency (if
there is one) is clearly in QT Creator (perhaps QT Designer?), not in the
API.
Perhaps there is an obvious way to do this in QT Creator's designer that I
am not seeing. From searching the mailing list archives, it seems that other
people have been confused by this as well, so I am not alone. Can you
suggest what I may be failing to see? If not, can you say whether you still
believe that this is an API issue rather than a QT Creator issue?
Thanks
Jonathan
On Fri, Sep 23, 2011 at 12:55 AM, <[email protected]> wrote:
> Hi,
>
> On 23 Sep 2011, at 08:07, ext Jonathan S. Shapiro wrote:
>
> > I am working in the most recent version of QT Creator. A notable
> deficiency in this version is that I cannot specify resources (e.g. Icons)
> that are "standard" from the Qt library. For example, I would like to
> specify the "standard" open file icon on the File|Open menu item. I see that
> this issue has been raised before as a bug.
> >
> > My question: is this addressed in Qt 4.7.0, or if not, is there enough
> interest that a patch would warrant enough attention to get critical
> evaluation?
> >
> > Bluntly: I'm willing to contribute a solution if the Qt team is willing
> to consider it. That said, if a solution is coming in 4.8.0 then I obviously
> don't want to replicate the work.
>
> Since this is a Qt question, not a Qt Creator one, you'd probably be better
> off using the qt-interest mailing list.
>
> Br, Eike
>
> --
> Eike Ziller
> Principal Software Engineer
>
> Nokia, Qt Development Frameworks
>
> Nokia gate5 GmbH
> Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany
> Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B
> Umsatzsteueridentifikationsnummer: DE 812 845 193
> Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori
>
> _______________________________________________
> Qt-creator mailing list
> [email protected]
> http://lists.qt.nokia.com/mailman/listinfo/qt-creator
>
>
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt-creator
