Dolphin 4.0 possible bugs or user ignorance

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Dolphin 4.0 possible bugs or user ignorance

Costas Menico-2
1)   Dragging and dropping a method from one class to another class,
containing the same method, will make the source method dissapear if
you are doing a move and answer not to overwrite. This is the same
behavior in 3.0.

Steps:
a) Make two methods with the same name in a class and subclass.
b) Drag and drop one method over the other holding down SHIFT key.
c) A message pops up warning about overwrite
d) Answer No.
e) The method being dropped still dissapears from the source class.

I would expect if you answer no that the source method remain in its
original class.


2)   Deleting a class causes an assertion failure in CHB. Although it
seems to work, You must close and reopen all CHBs.

I am not sure what the assertion failure means, but I am assuming I
should not be getting such a message and the CHB should be refreshed
properly.

When I try this in 3.0 I dont get the assertion failure.

Costas


Reply | Threaded
Open this post in threaded view
|

Re: Dolphin 4.0 possible bugs or user ignorance

Andy Bower
Costas,

> 1)   Dragging and dropping a method from one class to another class,
> containing the same method, will make the source method dissapear if
> you are doing a move and answer not to overwrite. This is the same
> behavior in 3.0.
>
> Steps:
> a) Make two methods with the same name in a class and subclass.
> b) Drag and drop one method over the other holding down SHIFT key.
> c) A message pops up warning about overwrite
> d) Answer No.
> e) The method being dropped still dissapears from the source class.
>
> I would expect if you answer no that the source method remain in its
> original class.

True. This sounds like a bug and we'll investigate.

> 2)   Deleting a class causes an assertion failure in CHB. Although it
> seems to work, You must close and reopen all CHBs.
>
> I am not sure what the assertion failure means, but I am assuming I
> should not be getting such a message and the CHB should be refreshed
> properly.
>
> When I try this in 3.0 I dont get the assertion failure.

I believe this was fixed in PL1. What Patch Level are you at.

Best regards,

Andy Bower
Dolphin Support
http://www.object-arts.com

---
Visit the Dolphin Smalltalk Wiki Web
http://www.object-arts.com/wiki/html/Dolphin/FrontPage.htm
---