[haiku-appserver] Re: Be's BView and BGLView (and BDirectWindow?) clipping info is faulty

  • From: "Rudolf" <drivers.be-hold@xxxxxxxxxxxx>
  • To: haiku-appserver@xxxxxxxxxxxxx
  • Date: Thu, 07 Apr 2005 18:26:29 +0200 CEST

Hi Axel,

> I cannot confirm this. The [1] array at the end of a structure is 
> often 
> used to indicate that the structure itself has a non specified 
> length. 

OK, so that's OK then :)

> This is only important if you have to copy the whole structure or 
> just 
> the clipping info. In BeUAE I used this to copy the clipping info and 
> it worked fine:
>       fClipListCount = info->clip_list_count;
>       if (fClipListCount > MAX_CLIP_LIST_COUNT)
>               fClipListCount = MAX_CLIP_LIST_COUNT;
>       memcpy(fClipList, info->clip_list, fClipListCount * 
> sizeof(clipping_rect));

Yep: tried that as well. Nogo!

That BeUAE: is that a GLView thing?

> Since the clipping info is specified in screen coordinates, I would 
> find it very odd if a BMenuBar (which is just a view) would mess the 
> clipping up, but who knows.
It's faulty. Maybe I'd better recheck if it's screen coordinates then: 
could be relative to left-top as well. But it's faulty.

> IIRC there is also a stars demo that uses both, a BMenuBar and a 
> direct 
> window - maybe that can give us a clue.
Maybe. But I expect we must conclude BWindowScreen is OK but BGLView is 
not at best. I can image the top-offset existing especially for BGL 
view BTW: I guess it's not that common (or possible at all?) that a 
DirectWindow has a menu?
(again: I'm new at this..)

Really: I spent a lot of time on BGLView now :-/

Thanks anyway..


PS: Textures up and running already: driver state is now active 
rendering :) (acc func's still turned off though: as they are not yet 
OK it seems)
Damn: the suspense is killing me :)


Other related posts: