On Tuesday 28 July 2015 14:51:49 Thiago Macieira wrote:
> Incentive: when my count drops to below 90, I will begin reviewing other
> people's changes again. It's currently at 111.
Down to 89. I'll start reviewing other people's contributions tomorrow when I
get to work.
That is, after the featu
Hi,
I have played with the tech preview of Qt3D 2.0 and I have some questions
and wishes.
1. Transparency. It does not seem like Qt3D handles transparency at all.
For instance, phong.frag always returns alpha=1.0. I would expect materials
like Qt3D::QPhongMaterial to have an opacity parameter and
On Monday 10 August 2015 02:36:20 Kevin Kofler wrote:
> Thiago Macieira wrote:
> > That is exactly what this proposal is not about. If you have a trait that
> > indicates your object type is trivially destrucible movable (a.k.a.
> > "trivially relocatable"), then we won't do memmove at all. We'll j
Thiago Macieira wrote:
> That is exactly what this proposal is not about. If you have a trait that
> indicates your object type is trivially destrucible movable (a.k.a.
> "trivially relocatable"), then we won't do memmove at all. We'll just do
> realloc, period.
realloc doesn't work if you are ins
On Sunday 09 August 2015 13:58:12 Kevin Kofler wrote:
> Thiago Macieira wrote:
> > On Sunday 09 August 2015 03:26:33 Kevin Kofler wrote:
> >> Marc Mutz wrote:
> >> > On Friday 07 August 2015 19:41:07 Kuba Ober wrote:
> >> >> How about making such traits explicitly necessary? People would then
> >>
Thiago Macieira wrote:
> On Sunday 09 August 2015 03:26:33 Kevin Kofler wrote:
>> Marc Mutz wrote:
>> > On Friday 07 August 2015 19:41:07 Kuba Ober wrote:
>> >> How about making such traits explicitly necessary? People would then
>> >> have to learn about them. As a user, I wouldn't mind - the com
