Re: FrameSvg and masks

2008-12-15 Thread Marco Martin
On Monday 15 December 2008, Ivan Čukić wrote: > > if you want to commit it no problem, > > Ok, committed, so whatever you want to change, feel free :) > > Cheerio > > BTW, I just noticed the getter for the prefix is > QString prefix() > while the setter(s) is (are) >void elementPrefix(...)

Re: FrameSvg and masks

2008-12-15 Thread Ivan Čukić
> if you want to commit it no problem, Ok, committed, so whatever you want to change, feel free :) Cheerio BTW, I just noticed the getter for the prefix is QString prefix() while the setter(s) is (are) void elementPrefix(...) :( too late for that? -- Money can't buy happiness, but neith

Re: FrameSvg and masks

2008-12-15 Thread Marco Martin
On Monday 15 December 2008, Ivan Čukić wrote: > On Monday, 15. December 2008. 3.39.07 Aaron J. Seigo wrote: > > On Sunday 14 December 2008, Marco Martin wrote: > > > Hi all, > > > speaking with fredrikh about speed with window masks some things have > > > emerged: returning a qbitmap is a bit wrong

Re: FrameSvg and masks

2008-12-15 Thread Ivan Čukić
On Monday, 15. December 2008. 3.39.07 Aaron J. Seigo wrote: > On Sunday 14 December 2008, Marco Martin wrote: > > Hi all, > > speaking with fredrikh about speed with window masks some things have > > emerged: returning a qbitmap is a bit wrong, since it will have to be > > converted to a qregion ea

Re: FrameSvg and masks

2008-12-14 Thread Aaron J. Seigo
On Sunday 14 December 2008, Marco Martin wrote: > Hi all, > speaking with fredrikh about speed with window masks some things have > emerged: returning a qbitmap is a bit wrong, since it will have to be > converted to a qregion each time, so.. > should the framesvg mask function return a qregion? th

FrameSvg and masks

2008-12-14 Thread Marco Martin
Hi all, speaking with fredrikh about speed with window masks some things have emerged: returning a qbitmap is a bit wrong, since it will have to be converted to a qregion each time, so.. should the framesvg mask function return a qregion? this would of course break the api, so quite of a problem