Issue 5204 in pharo: Workspace, Create textual references to dropped morphs doesn't work because of the morph's name returned by externalName

Status: New
Owner: ----
Labels: Milestone-1.3 Type-Bug

New issue 5204 by [hidden email]: Workspace, Create textual  
references to dropped morphs doesn't work because of the morph's name  
returned by externalName
http://code.google.com/p/pharo/issues/detail?id=5204

"Create textual references to dropped morphs" in a workspace doesn't work.
I think the problem is, that the
externalName of a Morph in Pharo is something like: 'a Morph(82051072)'  
whereas
externalName of a Morph in Squeak was 'Morph' and
'a Morph(82051072)' doesn't work as part of a variable Name.

So in Workspace>>acceptDroppingMorph: dropee event: evt inMorph:  
targetMorph there should perhaps be found another way to create a variable  
name for the dropped morph.


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

Comment #1 on issue 5204 by [hidden email]: Workspace, Create  
textual references to dropped morphs doesn't work because of the morph's  
name returned by externalName
http://code.google.com/p/pharo/issues/detail?id=5204

this is not limited to 1.3. i don't know how to change this. i accidentally  
selected it when entering the bug.


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

Comment #2 on issue 5204 by [hidden email]: Workspace, Create textual  
references to dropped morphs doesn't work because of the morph's name  
returned by externalName
http://code.google.com/p/pharo/issues/detail?id=5204

It is kind-of works,
i.e. when you enabling this option any morph which dropped into worspace  
inserts something like:

a morph(590348288)590348288

now i agree that it is not that useful.
But in order to fix that, we need to know what is expected behavior there.
Should the inserted text be (e)valuable, in terms that if you evaluate it,  
it will answer a reference to that morph?




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

Comment #3 on issue 5204 by [hidden email]: Workspace, Create  
textual references to dropped morphs doesn't work because of the morph's  
name returned by externalName
http://code.google.com/p/pharo/issues/detail?id=5204

At least that's what I expected.
You drop a Morph on a Workspace. The Morph slides back to where it was and  
leaves a variable that references the dropped Morph in the Workspace. You  
can now start sending messages to the Morph via that variable..
But not here, because "a morph(590348288)590348288" is no viable variable  
name.


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

Updates:
        Status: Accepted
        Labels: -Milestone-1.3

Comment #4 on issue 5204 by [hidden email]: Workspace, Create  
textual references to dropped morphs doesn't work because of the morph's  
name returned by externalName
http://code.google.com/p/pharo/issues/detail?id=5204

remove 1.3 tag. 1.3 will only get show-stopping fixes.


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