community
community copied to clipboard
Bug fixture for window opening while importing Window class
Issues addressed/ fixed (known to me atleast):
- #8340
- #8222
Changes done:
- Updated
EventLoop.ensure_windowfunction to work with lazy initialization of theWindowclass - Converted
_initializedtoBooleanProperty, changed initialized to read onlyAliasProperty, added lazy initialization of window Removed side-effects during window import, added lazy initialization of window. This would also help advanced users who want to use multiprocessing with Kivy without side-effects. Removed the bug thatWindow.initializedwas able to be changed/set by users, which should not be the case. MadeWindow.initializedread-only property. - Added new conifg value
lazy_window_initializationFor removing side-effects duringWindowinitialization, while maintaining backward behaviour compatibility, and also for advanced users who would want to have multiprocessing used with Kivy (without multiple window initialization), we added a config value namedlazy_window_initialization, which when set would lazily do the window initialization. - Updated the function
setupto properly work with lazy initialization feature ofWindow - Updated the fixture
kivy_appto properly work with lazy initialization feature ofWindow
Maintainer merge checklist
- [x] Title is descriptive/clear for inclusion in release notes.
- [ ] Applied a
Component: xxxlabel. - [ ] Applied the
api-deprecationorapi-breaklabel. - [ ] Applied the
release-highlightlabel to be highlighted in release notes. - [ ] Added to the milestone version it was merged into.
- [x] Unittests are included in PR.
- [x] Properly documented, including
versionadded,versionchangedas needed.