[bug #23954] setFont not implemented in nSTextStorage

[Fred Kiefer]

Follow-up Comment #4, bug #23954 (project gnustep):

Sorry, my fault. I change a sentence I wrote around, but didn't adjust the
words. What I wanted to say was, NSTextView (and the abstract class NSText)
both support setFont: in GNustep. For the class NSTextStorage this method is
only provided as a scripting extension and currently GNUstep doesn't provide
most of these extensions.

There wont be a problem to include this method if you really need it an
provide an implementation. OK, this is really easy, here is one (code stolen
from NSTextView), but why would we want it?

- (void) setFont: (NSFont *)font
{
  if (!font)
return;

  [self addAttribute: NSFontAttributeName
value: font
range: NSMakeRange(0, [self length])];
}

As soon as you provide a good reason for it, I will add this method to a
scripting category on NSTextStorage.


___

Reply to this item at:

  

___
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/



___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep

[bug #24083] Offset issues with the xmonad WM; blank windows with the cairo backend

[Yavor Doganov]

Follow-up Comment #2, bug #24083 (project gnustep):

I've never used xmonad, I just installed it to test this particular problem. 
Here is what the OP replied:

"I have no idea what business has GNUstep with window borders. The
application draws into its window and the window location on the screen and
decorations are the business of the window manager.

Just set the offsets to 0 when the windows are not reparented, and if
somebody complains they can get the them calculated properly. With typical
configuration you would be at most one pixel off even if the value was
actually useful for something."

The default window border size for xmonad is 1, it seems.

The grey windows with the cairo backend are unrelated to xmonad -- the OP
says he gets the same behavior with Window Maker.  Any clues what might be the
cause?  His machine is amd64 (aka x86_64), FWIW.

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/



___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep

[bug #24093] windowWillResize:toSize: apparently not called

[Fred Kiefer]

Follow-up Comment #1, bug #24093 (project gnustep):

Yes, this is a problem in the GNUstep code. In gui the only place where we
call windowWillResize: is in the setFrame:display: method, which is the one
place where we should not call it.
The underlying problem is that I currently don't see a way to get X events of
the resize before the resize has finished. Any idea welcome!

___

Reply to this item at:

  

___
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/



___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep

[bug #23661] Font size mismatch between cairo and art

[Fred Kiefer]

Follow-up Comment #4, bug #23661 (project gnustep):

I checked through the cairo commit log, but couldn't find anything related to
the problem. Not sure, when it got fixed and how. That makes it harder to add
a work around for older cairo libraries.

When I commited some changes to CairoFontInfo.m I also added a commented out
scale instruction. Could you please play with that line a bit? When we are
sure, that a proper value here would adjust your cairo fonts to a similar size
as the art fonts, then we could add something here for older cairo versions.
It could as well be that not the font size was incorrect, but the reported
metrics for that font. In that case you would get a similar layout as with
art, but the font itself would be smaller. Could you please report back on
that?


___

Reply to this item at:

  

___
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/



___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep

[bug #22898] openbsd gcc 2.95 compilation failure

[Riccardo mottola]

Update of bug #22898 (project gnustep):

 Open/Closed: In Test => Closed 


___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/



___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep

[bug #23968] on PRICE, the window doesn't get released after closure

[Riccardo mottola]

Follow-up Comment #2, bug #23968 (project gnustep):

I have verified and it appears to work on Linux and Freebsd with art and
xlib. I'd consider it fixed for now, thanks.

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/



___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep

[bug #23968] on PRICE, the window doesn't get released after closure

[Riccardo mottola]

Update of bug #23968 (project gnustep):

 Open/Closed: In Test => Closed 


___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/



___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep

[bug #23660] Drawing issues for control borders with art backend

[Fred Kiefer]

Update of bug #23660 (project gnustep):

  Status:None => Confirmed  
 Assigned to:None => FredKiefer 

___

Follow-up Comment #3:

I had a deeper look into this and it turns out that the original class
inspector panel looks fine even with the art backend. But due to size
differences that panel gets scaled up and art doesn't handle this well. The
horizontal lines get blured.
So this is nothing that could be corrected in Gorm, even when all the
inspectors are designed for the same size, a user could just resize the
window. Perhaps this change is still worthwhile, at least the default look
would be better.

I don't see much chance of improving this in the art backend. Perhaps we
could just note this as a limitation of that backend.

___

Reply to this item at:

  

___
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/



___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep

[bug #21690] xserver crashes with cairo backend and intel 82815 and XAA

[Fred Kiefer]

Follow-up Comment #3, bug #21690 (project gnustep):

Could you please try again with the latest cairo release and a newer GNUstep?
I would like to ge this bug report closed as we surely cannot resilve it from
our side.

___

Reply to this item at:

  

___
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/



___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep

[bug #24083] Offset issues with the xmonad WM; blank windows with the cairo backend

[Fred Kiefer]

Follow-up Comment #3, bug #24083 (project gnustep):

So there are two issues. One with the cairo backend and one with the xmonad
interaction.

For the cairo backend issue I will need to know which version of cairo and of
GNUstep are being used.

For the other problem I may need to explain first, why GNUstep tries to
determine the window border. In OpenStep it is possible to position the
contents of a window as well as the window itself, to do this reliable we need
to know about the border of the window. It even goes as far as positioning an
unmapped window, where we cannot determine the current border. That is why we
try to find out about standard windows borders when GNUstep starts up. 

For most modern window managers we have code to do this, perhaps we need to
add an extra bit for window managers that don't reparent a window. Here we
only get ConfigureNotify events (#22 in the log you send), perhaps we could
just rely on the border width given there.

___

Reply to this item at:

  

___
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/



___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep

[bug #23854] Scroll Wheel should be enabled when highlighting text in Terminal.app

[Fred Kiefer]

Update of bug #23854 (project gnustep):

  Item Group:None => Change Request 


___

Reply to this item at:

  

___
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/



___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep

[bug #24083] Offset issues with the xmonad WM; blank windows with the cairo backend

[Yavor Doganov]

Follow-up Comment #4, bug #24083 (project gnustep):

> I will need to know which version of cairo and 
> of GNUstep are being used. 

Based on his Debian suite, they are:

cairo 1.6.4
Base 1.16.1
Gui/Back 0.14.0

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/



___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep

[bug #21690] xserver crashes with cairo backend and intel 82815 and XAA

[Eric Wasylishen]

Follow-up Comment #4, bug #21690 (project gnustep):

Hi,
The problem has gone away :)
I upgraded to Ubuntu 8.04 as well as the latest GNUstep svn version, and the
cairo backend works very well now.
Thanks,

Eric

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/



___
Bug-gnustep mailing list
Bug-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnustep