This should be safe enough, but as Jelly Roll said, "One never knows,
do one."
Here is the checkin log:
QQQQQ
Many *disabled* changes re failed single-load plan: the present code
should be equivalent to previous rev.
All unit tests pass, pylint is happy, as am I.
The new code is mostly guarded with the new_init switch. Noteworthy
other code...
leoCommands.py:
Added the following organizer methods to c.__init__:
self.initCommandIvars()
self.initDebugIvars()
self.initDocumentIvars()
self.initEventIvars()
self.initFileIvars(fileName,relativeFileName)
self.initOptionsIvars()
self.initObjectIvars()
# Initialize all subsidiary objects, including subcommanders.
self.initObjects()
This is active in the present code base.
leoGlobals.py:
- Moved the following trace from leoKeys.py to leoGlobals.py:
trace_masterCommand = False
trace_minibuffer = False
- Created k.defineSettingsIvars, containing all calls to
c.config.getX.
This is active in the present code base.
plugins/backlink.py:
- The top-level init method returns False if we are using the nullGui.
I'm not sure how this happened, but it did happen during unit
testing.
qtGui.py:
- Added guards for self.top for several methods.
These are not likely to be used in the new plan, but such guards
can't hurt.
QQQQQ
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
