Dolphin Options problems

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

Dolphin Options problems

John Aspinall-3
Problems with the Dolphin Options editor:

1) It's easy to screw things up by accidentally dragging one option onto
another, e.g. drag Workspace>>defaultFont onto defaultView then try to open
a Workspace (lots of other possibilities too!). Maybe confirm any such
operations?

2) Dragging an item onto a top-level item gives error 'SortedCollection
should not implement #at:put:'

3) Selecting Workspace>>defaultView gives 'a SmalltalkWorkspaceDocument does
not understand setter message #defaultView:' repeatedly.

John


Reply | Threaded
Open this post in threaded view
|

Re: Dolphin Options problems

Blair McGlashan
John

Thanks for your bug reports.

You wrote in message news:[hidden email]...
> Problems with the Dolphin Options editor:
>
> 1) It's easy to screw things up by accidentally dragging one option onto
> another, e.g. drag Workspace>>defaultFont onto defaultView then try to
open
> a Workspace (lots of other possibilities too!). Maybe confirm any such
> operations?
>
> 2) Dragging an item onto a top-level item gives error 'SortedCollection
> should not implement #at:put:'

I think these problems also existed in 4.0 (see for example:
http://www.object-arts.com/Lib/EducationCentre4/htm/cautions.htm).

I have an idea for improving this (basically to prompt if one attempts to
change the value of an aspect to an incompatible class), but failing that I
think we should just disable drag&drop in that view as it is too easy to do
it by mistake when attempting to select something. I've recorded these as
defect #473.

> 3) Selecting Workspace>>defaultView gives 'a SmalltalkWorkspaceDocument
does
> not understand setter message #defaultView:' repeatedly.

Defect #474.

Regards

Blair


Reply | Threaded
Open this post in threaded view
|

Re: Dolphin Options problems

Andy Bower
John,

> > Problems with the Dolphin Options editor:
> >
> > 1) It's easy to screw things up by accidentally dragging one option onto
> > another, e.g. drag Workspace>>defaultFont onto defaultView then try to
> open
> > a Workspace (lots of other possibilities too!). Maybe confirm any such
> > operations?
> >
> > 2) Dragging an item onto a top-level item gives error 'SortedCollection
> > should not implement #at:put:'
>
> I think these problems also existed in 4.0 (see for example:
> http://www.object-arts.com/Lib/EducationCentre4/htm/cautions.htm).
>
> I have an idea for improving this (basically to prompt if one attempts to
> change the value of an aspect to an incompatible class), but failing that
I
> think we should just disable drag&drop in that view as it is too easy to
do
> it by mistake when attempting to select something. I've recorded these as
> defect #473.

As Blair mentions, the hazards of drag and drop in the PAI were present in
Dolphin 4. I think the facility was added in a frenzy of enthusiasm after we
got D&D working in Dolphin originally. Personally, I've hardly ever used the
D&D in the PAI and therefore have decided to remove it. In the
FlipperInspector this situation is also more symmetrical since the
InstVarInspector currently doesn't support D&D at all.

Best Regards,

Andy Bower
Dolphin Support
http://www.object-arts.com
---
Are you trying too hard?
http://www.object-arts.com/Relax.htm
---