Michael Can you try this then and tell me if I got it right? Sorry I am not savvy enough to combine the removal of the class with the rest of the changes made. When I try to us the change sorter to add that change, I just get a nil, and I can't figure out how to manually add it into the file without getting an error when I load it...sigh...
Anyway, the toggle full screen menu options work, the labels update appropriately, and if for some reason someone wants to us the full screen button on TheWorldMainDockingBar, it works too. These are just instance methods of DisplayScreen now, and I referenced Display where appropriate. Maybe you could tell me if I did this right and tell me how to properly upload to the Pharo inbox? If you don't mind for this simple thing, then perhaps I could do other such simple tasks for you in the future. I don't mind doing things like this that I can handle and contributing somehow when someone just needs grunt work like this done. I'm sure I would learn some things along the way... Take care, Rob On Mon, Feb 23, 2009 at 11:13 PM, Michael Rueger <[email protected]> wrote: > Rob Rothwell wrote: > > The class side methods seem easy enough to move to the instance side of > > DisplayScreen so that the global Display can execute them. Just some > > hunting down of the senders of those methods to do. All that remains on > > the instance side is: > > > > ScreenController>>objectForDataStream: refStrm > > Yes, that can just go away with the class. > > Michael > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
RemoveScreenController.1.cs
Description: Binary data
RemoveScreenControllerClass.1.cs
Description: Binary data
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
