Didn't seem to have any effect.  The broken windows are still there, and
the file size is still 99.5MB.

On Tue, Dec 9, 2014 at 8:49 PM, Mariano Martinez Peck <[email protected]
> wrote:

> The size could have been the Monticello cache for all the stuff you loaded?
> In the big image try ImageCleaner new cleanUpForRelease, then save it and
> compare size.
>
> CHeers,
>
> On Tue, Dec 9, 2014 at 9:22 PM, stepharo <[email protected]> wrote:
>
>> This is indeed quite strange.
>>
>> Le 9/12/14 14:31, dboeren a écrit :
>>
>>  OK, some progress.  I made a copy of Pharo to experiment with and found
>>> World->Windows->DeleteAllWindowsDiscardingEdits.
>>>
>>> This destroyed the three rogue windows and at least to a first glance the
>>> system is working correctly again.
>>>
>>> But, I also still have the original copy which is still malfunctioning.
>>>
>>> Ready for more weird?  The broken copy of Pharo is 99.5MB.  The working
>>> copy
>>> is only 70.2MB.
>>>
>>> Here is the full list of what I did to create the working copy:
>>> 1.  Copy/paste the Pharo3.0 file in OSX Finder, rename it to "Pharo 3.0
>>> test"
>>> 2.  Open Pharo 3.0 Test
>>> 3.  World->Windows->DeleteAllWindowsDiscardingEdits
>>> 4.  Recreate my 3 windows (Workspace, Transcript, Browser) and resize
>>> them
>>> to approximately the same layout I had before
>>> 5.  Quit and save the new image
>>>
>>> So whatever was wrong with those three windows was taking up 29.3MB?
>>> That's
>>> really bizarre...
>>>
>>> If someone knows how to debug this sort of thing I can upload my
>>> corrupted
>>> copy to you and perhaps that would be the best way to shed some light,
>>> but
>>> at least I seem to have a working environment again so I can proceed on
>>> the
>>> next step of my program :)
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context: http://forum.world.st/Left-
>>> mouse-button-not-working-in-Pharo-3-0-tp4795107p4795126.html
>>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
>>>
>>>
>>>
>>
>>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>

Reply via email to