Re: Bugs in gui/back

[Andreas Höschler]

Hi all,

I just found ./gnustep-gui-0.25.1/Documentation/manual/theviewconcept.texi and suppose that the problem is caused by the optimization mentioned in this document. It seems critical calls (that MacOSX at least still performs) to NSWindow::drawRect: are skipped now. 

Any hint where to look is greatly appreciated. I wold love to get the new GNUstep tree working ...

Thanks in advance,

 Andreas

On Apr 20, 2018, at 2:50 PM, Andreas Höschler wrote:

I currently have a window with just one button and a spacer above and below it and am trying to resize the window vertically which works. However, 

NSWindow:

- (void)setFrame:(NSRect)frameRect display:(BOOL)flag

is never called when I do this which is probably the reason why auto relayouting the content does not work. On MacOSX (same sources) I get a bunch of 

2018-04-20 14:36:31.770 TabTest[8909:903] setFrame {{26, 282}, {97, 124}} display 1
2018-04-20 14:36:31.780 TabTest[8909:903] setFrame {{26, 285}, {97, 121}} display 1
2018-04-20 14:36:31.804 TabTest[8909:903] setFrame {{26, 287}, {97, 119}} display 1
2018-04-20 14:36:31.831 TabTest[8909:903] setFrame {{26, 288}, {97, 118}} display 1
2018-04-20 14:36:31.881 TabTest[8909:903] setFrame {{26, 289}, {97, 117}} display 1
2018-04-20 14:36:31.931 TabTest[8909:903] setFrame {{26, 289}, {97, 117}} display 1
...

calls when I vertically resize the window and the content is relayouted just fine!?

Any idea where to look from here? Which part in GNUstep is responsible for sending setFrame:display: to NSWindow when dragging the window larger and smaller?

Mit freundlichen Grüßen,

Andreas Höschler

Managing Director

Smartsoft GmbH

Birkenweg 11a

21483 Gülzow

Tel: 040 60889019

Web: http://www.smartsoft.de

EMail: ahoesch@smartsoft.de