Awesome! Glad I could help.
-mandeep
On Tue, Nov 17, 2015 at 5:40 AM, Welbourne Edward
wrote:
> Hi again Mandeep,
>
> Thanks for that.
>
>> Accepted: 1446367200
>> Ignorant of DST (-> 1): Sun Nov 1 01:40:00 2015
>> Accepted: 1446370860
>> Ignorant of DST (-> 0): Sun Nov 1 01:41:00 2015
>
> O
Hi,
on newer Windows systems some stock icons come in a wealth of sizes for
various scaling needs. For example, on Windows 10 some icons are available
in 11 different sizes! (Including 256x256.) Hardcoding a "small" and
"large" size doesn't really do them justice (even if you'd consider the
"shell"
Hi again Mandeep,
Thanks for that.
> Accepted: 1446367200
> Ignorant of DST (-> 1): Sun Nov 1 01:40:00 2015
> Accepted: 1446370860
> Ignorant of DST (-> 0): Sun Nov 1 01:41:00 2015
OK, fun - now I know when at least one implementation changes over within the
hour !
Eddy.
On Sat, Nov 14, 2015 at 2:03 PM, Frank Richter wrote:
> Of course I'd very much like to see this make it; however, I think that
> before starting to submit individual patches for review maybe a bit of
> "approach review" might be a good idea.
> * Are these changes desireable?
> * What do you think
Hi,
For the first point I think it is a good idea.
However the second point seems to be already taken care of. As far as
i know, the current API for obtaining such icons is
QStyle::standardIcon(), looking at its implementation in QCommonStyle,
it calls QPlatformTheme::standardPixmap() for multipl
Could something be done about that?
Users don't have any control over undo/redo stack other than pausing or
resetting it and no way to directly access it.
Also, some functions reset undo stack for no reason while others, similar
ones don't. I was baffled that insertHtml doesnt reset undo stack an
> Namespaced builds are only tested on Linux IIRC, not os x. Similarly
> static builds happen for ios, where the plugin loading code is
> probably not used.
ah, that explains why all namespaced build failures that i saw were on
osx :)
___
Development ma
