Found the syntax error (at least as far as Python 2.6.6 was concerned) that was preventing wizards from being enabled. Fixed in svn.
Thanks for getting that. I've been using 2.7.1 for a while now, didn't think about lower versions. I guues I should setup 2.6 on a vm or something for testing.
In the long run I do think this will be a slowdown, but do as you will... no performance diff yet.
War implemented the wizard images feature I asked for, what about performance there, considering they will already be on your hard drive extracted in the mopy folder.
As far as I know,It will look in your archive first, then if not in the archive, use the default image in the wizard images folder from mopy if not found in the archive.
Thanks for the feedback. From my testing, I didn't see any significant slowdowns, but I also don't have a low end computer or anything so :shrug: Also, you are correct on the 'Wizard Images' folder search preference.
Wrye Python 03a with svn 900 (myk002's syntax error fix) - It works but there's still a minor problem, I broke it

:celebration: ( okay maybe a little too much gloating

)
http://www.bild.me/bild.php?file=6859781Untitled.jpg
I must say though from a user viewpoint - Speed of selections on the last run through without trying to break it was remarkably better than usual. And particularly for AWLS with resized wizard larger the screens presentation is better encompassing the whole image as opposed to previously just seeing just four fifths of some images.
Summary:
Resize works - But does not hold its position the next time a wizard is invoked, reverts to a default size.
Speed of execution of wizards is very much improved
Going backwards after getting half way through / then forwards making selections to the end / then backwards quickly (impatient user click click click click click) = Error in the script flagged for AWLS 5.5.2
Edit: Forgot to mention; Double clicking any screenshot in the wizard with the magnifying glass loaded it up successfuly in my associated program (currently Paint.net)
Sounds like there's still some issues with the "Back" button then. Might be some strangeness from clicking excessively, or more likely just a straight up logic error on my part. I can't promise anything for a while, 'cause it looks like I'm going to be stuck in San Diego for ~2 weeks before I get home. So my developing will be done without internet

, and any committing I make will be without my dev computer :verymad:
I'll look at putting in wizards remembering their last size as well at some point.