would be good to address that (even if we are rewriting slowly everything) or we should rewrite faster. Stef On May 22, 2012, at 10:47 AM, Camillo Bruni wrote:
yep, I fork :), but I didn't adapt the UI to cope with it, since I was told that the whole UI will be rewritten in 2.0 anyway (side kick to ben).
On 2012-05-22, at 09:33, Mariano Martinez Peck wrote:
On Tue, May 22, 2012 at 5:46 AM, Igor Stasenko <siguctua@gmail.com> wrote: we had same issue lately with Stef. is there a fork introduced somewhere into MC code?
I think it was one of the things camillo did to improve performance with large package-cache but I may be wrong.
On 22 May 2012 01:26, Fernando Olivero <fernando.olivero@usi.ch> wrote:
I haven't experienced it.
To recover: The trail generally happens when you have to UI process installed. Terminate the extra one and things will be back to normal. (try with both, and the current UI process will tell you it cant be killed).
Fernando
On Tue, May 22, 2012 at 12:24 AM, Sean P. DeNigris <sean@clipperadams.com> wrote:
Every time I go to save a package in the latest 2.0, the world gets messed up like http://code.google.com/p/pharo/issues/detail?id=5013. It seems to start when I click "Save" and the commit message editor comes up. If I drag it around, it leaves a trail (the Process Browser shows a "nil" process at the UI priority in addition to the UI process). Once I accept the comment, MC Browser gets that big red X thing replacing the list on the left.
Is anyone else seeing this?
Sean
-- View this message in context: http://forum.world.st/Monticello-Browser-messing-up-Morphic-tp4631248.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- Best regards, Igor Stasenko.
-- Mariano http://marianopeck.wordpress.com