Ed Leafe wrote:
I'm still working on the Designer, but it's not the easiest thing to create. And since the Designer is written in 100% Dabo code, all the recent changes done to the UI framework broke a lot of the Designer stuff. Hey Paul, let's make sure to at least give the Designer a run-through before making any more UI overhauls like the recent grid changes. While those changes were probably worthwhile, they certainly set the Designer progress back quite a bit.
Are you still running into problems or is it looking smooth now? I had the grid changes in a separate branch for about a week before merging into the trunk, but only heard about the designer problems a couple weeks after that. You had been having problems with the grid prior to my changes so it wasn't straightforward sorting out what I caused versus what was already there.
Admittedly, I didn't test the grid editor stuff but assumed it would work in parallel with the renderers, and making assumptions like that is always a bad idea.
I'll try to remember to include the designer in my test suite before committing stuff from now on... actually, what bit me there was that the designer was the only place using grid editors, but since I've added an editor test to dGrid.py, that particular problem won't surface again.
-- Paul McNett http://paulmcnett.com http://dabodev.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
