On 11 February 2010 04:42, James Paige <[email protected]> wrote:
> On Wed, Feb 10, 2010 at 07:57:19PM +1300, Ralph Versteegen wrote:
>> On 10 February 2010 19:53, James Paige <[email protected]> wrote:
>> > On Tue, Feb 09, 2010 at 10:47:27PM -0800, [email protected] 
>> > wrote:
>> >> james
>> >> 2010-02-09 22:47:27 -0800 (Tue, 09 Feb 2010)
>> >> 71
>> >> Okay, frame_cropped_view was still all wrong. Think it is right now...
>> >
>> > I am working on fixing up edgebox to crop without ever calling setclip,
>> > but I am making a mess of things. I'll have to sort it out tomorrow.
>> >
>> > ---
>> > James
>>
>> Why are you doing that? Just for the sake of getting rid of setclip?
>> Like I said before, I think getting rid of setclip is more trouble
>> than it's worth: rewriting edgebox not to use setclip will make it
>> extremely messy. setclip is safe as long as you only call it before
>> calling a primitive drawing function.
>
> Not for the sake of getting rid of setclip, just for the sake on not
> using it in edgebox. Then it seems to me that it would be possible to
> call setclip once before edgebox and have it work right... but of course
> that doesn't jive well with my previously stated plan doing slice
> drawing with views... Like I say, I am still feeling clumsy with this
> clipping stuff..

OK. Assuming you were thinking of replacing the setclip calls with
frame view creation calls, that won't work, as each draw to a another
view will reset the clip.

>> Anyway, if you're stopping for today, then I'll do
>> slice-clipping-using-views right now.
>
> Yay! :)
>
> ---
> James

Working on it now. After staring at it for a loooong time, I've
finally worked out the simplest way to get around the
each-view-has-its-own-origin problem. (Next time, I'll use git for
this sort of thing, rather than leave something temporarily broken
while I figure out how to restore it)
_______________________________________________
Ohrrpgce mailing list
[email protected]
http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org

Reply via email to