If you want to do it as part of your application, maybe** look into sender
and implementers of #acceptDroppingMorph:event:
cheers -ben
** I have no great experience with this. Just had a poke around for an
answer.
On Sun, Feb 8, 2015 at 7:21 AM, Sven Van Caekenberghe wrote:
> Yes, but please do
Yes, but please don't just limit it to UI things.
I want to be able to 'Copy an object' to an 'Object Clipboard' when I am on
'self' in an Inspector. And I want to be able to 'Paste an object' in a slot of
an Inspector, or wherever that makes sense.
I always emulate this with a global, like XXX
Indeed, this is a little feature a proper object-oriented environment
should not miss :)
Doru
On Sun, Feb 8, 2015 at 12:02 AM, Damien Pollet <
damien.pollet+ph...@gmail.com> wrote:
> What if inspectors and workspaces were able to copy-paste object
> references?
> When pasting, a new binding woul
What if inspectors and workspaces were able to copy-paste object references?
When pasting, a new binding would be made with some automatic name.
I always wondered why this was not part of Morphic…
On 7 February 2015 at 23:52, Hernán Morales Durand wrote:
> I see! something like?
>
> self addMor
I see! something like?
self addMorphCentered: (EllipseMorph allInstances detect: [ : i | i name =
'an EllipseMorph(485752832)' ])
2015-02-07 19:39 GMT-03:00 Sean P. DeNigris :
> hernanmd wrote
> > Use the halos... select the Menu halo (red) -> debug... -> explore morph
>
> Yes, you can bring up
hernanmd wrote
> Use the halos... select the Menu halo (red) -> debug... -> explore morph
Yes, you can bring up an inspector/explorer on each morph, but the hiccup is
how do you connect them i.e. send one as an argument to the other?
-
Cheers,
Sean
--
View this message in context:
http://f
2015-02-07 19:28 GMT-03:00 nacho <0800na...@gmail.com>:
> @Hernan
> Sending a message to an object using the inspector allows me to do:
> self addMoprh: EllipseMorph new.
>
> But what I want is to add a morph to another morph that is already
> instantiated.
>
Use the halos.
In Windows is Alt+Shif
@Hernan
Sending a message to an object using the inspector allows me to do:
self addMoprh: EllipseMorph new.
But what I want is to add a morph to another morph that is already
instantiated.
I want to reference the object that is somewhere in the memory an be able to
manipulated even if I have not
nacho wrote
> How do I achieve this?
Two options:
1. (Unscalable hack) Identify them by a unique feature of their description
e.g. "(World submorphs detect: [ :e | e color = Color blue ]) addMorph:
(World submorphs detect: [ :e | e isKindOf: EllipseMorph ])"
2. Bring back a feature like that of Ma
2015-02-07 17:46 GMT-03:00 nacho <0800na...@gmail.com>:
> Hi,
> Suppose I do:
> Morph new openInWorld
>
> and then:
> EllipseMorph new openInWorld
>
> without referencing them to a variable.
> How do I access those objects?
>
Morph new openInWorld inspect.
Morph new openInWorld explore.
or
Morp
Hi,
Suppose I do:
Morph new openInWorld
and then:
EllipseMorph new openInWorld
without referencing them to a variable.
How do I access those objects?
Since the only thing I know is that is a "a Morph(428605440)" and a "an
EllipseMorph(448004096)"
If I want to Morph(428605440) addMorph: EllipseMor
11 matches
Mail list logo
