Status: New Owner: ---- Labels: Type-Defect Priority-Medium
New issue 595 by damien.c...@gmail.com: [Glamour] Transmission>>from: is said to take a port http://code.google.com/p/moose-technology/issues/detail?id=595
The method GLMTransmission>>from: takes a parameter 'aPort'. However, this method is most of the time used with a pane symbol instead of a port. This is confusing as the Moose book says
" For specifying a transmission origin that points to a #selection port of a pane, you simply use from:. "
In this case it is clear that the port is #selection and it is the default. The reader is then waiting for an implementation similar to:
GLMTransmission>>from: aPaneSymbol ^ self from: aPaneSymbol port: #selection
Updates: Labels: Component-Glamour
Comment #1 on issue 595 by tudor.gi...@gmail.com: [Glamour] Transmission>>from: is said to take a port http://code.google.com/p/moose-technology/issues/detail?id=595
The problem is that beforehand we only had from: which could receive either a symbol for the pane, or an association for the port. This was bad, and now Glamour offers from:port:, but there are still legacy cases of from: being called with an association.
The Moose Book does not talk about this, because we want to go away from it. But, at the moment, it won't get fixed.
Updates: Status: Fixed Labels: Milestone-4.4
Comment #2 on issue 595 by tudor.gi...@gmail.com: [Glamour] Transmission>>from: is said to take a port http://code.google.com/p/moose-technology/issues/detail?id=595
For the moment, the solution is to add a comment explaining the situation.
Name: Glamour-Scripting-TudorGirba.118 Author: TudorGirba Time: 1 May 2011, 1:57:50 am UUID: cc6a591b-ca5c-4b56-a575-4d54bf9d5f06 Ancestors: Glamour-Scripting-TudorGirba.117
added comment to address issue http://code.google.com/p/moose-technology/issues/detail?id=595
-
moose-technology＠googlecode.com