Hi,
actually, that is not quite what we want to do (we meaning my son and I
in our first squeak project).
Since we were unable to assemble the message, we ended up doing a
brute force method to get it to work:
lockCell: aBoolean row: aRow column: aColumn
self addressToCellNumber: aRow
Hi Louis,
Thanks, your advice looks very good here we hadn't even thought about
ordered collections (we studied the Squeak by example book before we
started our project, but sometimes it's hard to figure out when exactly
you might need to use stuff you read about, even if you do the examples)
..
On 24.04.2012, at 10:59, Dawson wrote:
.. I had thought there might be a way of building up the cellObject
cellLock: aBoolean ... judging from the replies, it seems that it is
either a) crazy, b) it can't be done, c) no one knows how to do it.
It's a) crazy.
Of course there's a way to do
Hi,
I've read the sparse documentation on 'dynamic message' calls and I've
experimented a lot and still cannot figure out how to do something that
should be simple:
I want to build a message like this:
cellObject cellLock: aBoolean
where cellObject is to look like: cell1,
Hi,
For your example:
cellObject cellLock: aBoolean
where cellObject is to look like: cell1, cell2, cell3 ..., or cell9
I don't think you want or need to use #perform:. You use #perform: when
you want to construct the message name and sent the constructed message
name to an object.
Ah that's curious - your reply did not have a Re: and was not threaded with the
original message. Would have saved me to write a message very similar to yours
;)
- Bert -
On 23.04.2012, at 10:44, Louis LaBrunda wrote:
Hi,
For your example:
cellObject cellLock: aBoolean
where
