inspector and auto-update

Hi I noticed that in the past (likely some current squeak image)
 When you brought up an inspector on an object it would auto-update the instance variables shown.

However this behaviour is lacking in a
PharoCore1.0rc1
Latest update: #10502

So is that what is expected?

--
===========================================================================
John M. McIntosh <[hidden email]>   Twitter:  squeaker68882
Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
===========================================================================





_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

On Jan 6, 2010, at 9:32 PM, John M McIntosh wrote:

> Hi I noticed that in the past (likely some current squeak image)
> When you brought up an inspector on an object it would auto-update the instance variables shown.
>
> However this behaviour is lacking in a
> PharoCore1.0rc1
> Latest update: #10502
>
> So is that what is expected?
>

auto-update is supposed to work with the inspector... if not, it's a bug.

        Marcus
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

On Wed, Jan 6, 2010 at 9:41 PM, Marcus Denker <[hidden email]> wrote:
>> However this behaviour is lacking in a
>> PharoCore1.0rc1
>> Latest update: #10502
>>
>> So is that what is expected?
>>
>
> auto-update is supposed to work with the inspector... if not, it's a bug.

the NewInspector does not support this feature if I remember correctly.

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Lambdas are relegated to relative obscurity until Java makes them
popular by not having them." James Iry

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

NewInspector is not in Core.

What I've noticed is AutoUpdating of inspector values stopping to work under certain circumstances, like a halt raising a debugger while the inspector is selected.
Rather certain this has to do with terminated threads caused by debugger opening, similar to a MessageTally never popping up if you encounter a halt in code after MT is started.

Cheers,
Henry

On Jan 11, 2010, at 11:16 14AM, Damien Cassou wrote:


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

On Mon, 11 Jan 2010, Damien Cassou wrote:

In this case it's not an inspector, but an explorer, the name is
misleading.


Levente

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project