So, now in such cases the main UI should actually show up, although your plugin's UI might look weird due to theming not being properly applied.
#Size of elite dangerous download code#
mouse in/out, causes the theme.py code for that to trigger. This also applies if you set up a button such that enter/leave on it, i.e.
This then caused the whole application UI to never show up on startup. a plugin was failing due to Python 3.10 using collections.abc instead of collections, and the plugin's custom widget had a configure() method which was called by the core theme code on startup or theme change.
If you use a sub-class for a widget the core code will no longer break if your code raises an exception. NearestDestination being empty, which the schema allows. This prevents the big 'Code圎ntry had empty string, PLEASE ALERT THE EDMC DEVELOPERS' message from triggering on, e.g. This release addresses some issues with newer EDDN code which could cause erroneous alerts to the player, or sending of bad messages.ĮDDN: Cope with ApproachSettlement on login occurring before Location, such that we don't yet know the name of the star system the player is in.ĮDDN: Cope with ApproachSettlement missing planetary coordinates on login at/near a settlement in Horizons.ĮDDN: Change the Code圎ntry "empty string" checks to only apply to those values where the schema enforces "must be at least one character".