After talking with John I've checked in my patch, but filed
http://bugzilla.osafoundation.org/show_bug.cgi?id=2401

to track the fact that it leaves garbage in the repository - its assigned to me for now

is there a bug for could-based deletion so I can make this one dependent on it?

Alec

John Anderson wrote:
Alec Flett wrote:

I talked with Bryan, Andi, and John -
- john says that the "reload parcels" crash is due to a bug with jed's minicalendar - but that it would be nice to reload without quitting.

I'll try to add "deleting the blocks in the soup" (with a fix for your child block bug described below) to reload parcels, and check in a workaround for jed's bug

- even if we were to reload the parcels, we'd still need to blow away the soup. That would require tearing down and rebuilding the wx widget tree. yuck.

Actually, tearing down and rebuilding the wxWidget tree is only two lines:
wx.GetApp().UnRenderMainView ()
wx.GetApp().RenderMainView ()

- I agree that it would be nice to add the ability to reload without quitting, but it was a whole lot less work to just add a command line option that blows away the soup.

I filed a bug for this, and attached a patch. if you'd like to review it, check out:
http://bugzilla.osafoundation.org/show_bug.cgi?id=2394

It looks like your patch only deletes the topmost block of the tree, but not all the children blocks, which become garbage that is never cleaned up.

I also added the CPIA Viewer I mentioned earlier, that lets you conveniently view the block hiearchy in the soup. I'll check it in after I add delete to block reloading.


I'll check this in later today if that's ok with everyone

Alec

Alec Flett wrote:

I've been hacking some parcel.xml's to change some UI, and even though the repository seems to notice the changes I make every time I start up, the UI isn't actually updating. I'm assuming this is because items were originally copied into the soup, and even though the original items in the repository have been changed to match my parcel.xml, the soup remains as it is.

So I've been trying to figure out if there is a way to "reload the soup"... i.e. blow away the existing soup and force a new soup to be created.

Any ideas? Is there maybe some command line flag that could do this for me that I'm missing?

Alec

------------------------------------------------------------------------

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
 


------------------------------------------------------------------------

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
 



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev

Reply via email to