jamesgkent / memtkinter Goto Github PK

if toplevel window is destroyed without the main window being destroyed leads to issues.
if we try to save then the parent node will not exists so it errors.
if we restructure pysettings to be able to get parent node the settings will be lost when the parent saves.
if we leave the settings object as a child of the parent settings object the window from which it will try to get attributes will no longer exist.

ultimately we need to way to trigger the capture of callable attributes without saving, so when the save does happen the attributes have been captured as literals.

all widgets need thorough documentation, particularly the mega widgets, mixins and enhancements

implement auto scrollbar versions of:

• listbox
• text
• canvas

implement:

• multi widget scrollbar
• specialized multi scrollbar for listboxes

some config args should be passed to outer widget, others to inner, these should be filtered to pass them to the relevant place?
or a flag could be added to control whether passed to inner or outer..