[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: What happened to the code freeze?

From: Doug Simons
Subject: Re: What happened to the code freeze?
Date: Wed, 21 Apr 2010 13:26:15 -0600

Okay, here are the files I updated for this fix to NSMenu. These are based on r30210 if you want to do a diff to see what's changed. Or drop them in and see how it works for you (Eric, I agree that this should help with the scroll wheel in Ink. Let me know. Also, try typing very fast in a text view before and after applying this change).

Fred and anyone else who takes a look: let me know in the next day or so if you see any issues here or have any questions. I'll hold off checking them in for the moment.



Attachment: NSApplication.m
Description: Binary data

Attachment: NSMenu.h
Description: Binary data

Attachment: NSMenu.m
Description: Binary data

Attachment: NSMenuItem.m
Description: Binary data

On Apr 21, 2010, at 12:11 PM, Gregory Casamento wrote:

The feature freeze only includes core (make, base, gui and back).   I
don't really consider the WinUXTheme (or any of the themes) to be part
of the freeze, so your changes are fine where they are.

I should have been more concise about the scope of the freeze I wanted
in the first place.  That would have avoided some of the current

I would like Doug to send the patches he's got in mind to Fred for
review and testing.


On Wed, Apr 21, 2010 at 2:04 PM, Eric Wasylishen <address@hidden> wrote:
Sorry, two of my recent theme-related commits were probably inappropriate to
make  during the feature freeze (adding an option to disable the inner
border in NSScrollView, and moving NSBrowser header drawing to GSTheme). I
can revert these if you'd like.
Doug: the Windows menu fixes sound great. I was noticing a lot of menu
flickering with the WinUX theme, and mousewheel scrolling in Ink was really
laggy - I bet your patch will fix those problems.
On Wed, Apr 21, 2010 at 11:32 AM, Gregory Casamento
<address@hidden> wrote:

I believe that "feature freeze" is the correct term and what I was
really after when I suggested the freeze.   I'm comfortable with any
changes that fix or improve existing functionality so long as:

1) they don't add new features and
2) They don't involve drastic refactoring of existing code.


Gregory Casamento - GNUstep Lead/Principal Consultant, OLC, Inc.
yahoo/skype: greg_casamento, aol: gjcasa
(240)274-9630 (Cell)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]