Bug #937

problem with relative model/address binding for jcom.receive|send|view in view patcher

Added by Théo de la Hogue about 9 years ago. Updated over 7 years ago.

Status:ClosedStart date:2011-09-01
Priority:HighDue date:
Assignee:Théo de la Hogue% Done:


Category:-Spent time:-
Target version:MVC for 0.6
Branch:master OS:


I described the the problem for the jcom.receive first.

If you put a [jcom.receive model/address] into a view patcher
the jcom.receive will bind on /myModel/model/address and not
on /myView/model/address : that's normal and that is what we want.

but how to get back the value of the model/address parameter of the
jcom.hub of a view patcher ? that's the problem.

an other side effect for a [jcom.view model/address] into a view patcher :
it will create another instance of model/address.1 because it is already
an internal parameter made by the hub...

here the solution could be to warn the user that he is doing something dangerous
but I'm not sure it is the good solution...

Related issues

Related to Modular - Feature Request #964: remote access for parameter|message|return registered in ... Rejected 2011-09-29


#1 Updated by Théo de la Hogue over 8 years ago

a beginning of solution could be to rename the "model/address" internal return (in model case) | parameter (in view case).

The new name would be simply "address" and would store the effective absolute address of the model or of the view and it would be always a return.

Then, in a view context, the jcom.hub would have another "bind/address" parameter (or any other name you prefer).

This implies to change the way jcom.receive, jcom.view, ... binds to focus on "address" in model patcher or on "bind/address" in view patcher.

#2 Updated by Théo de la Hogue over 7 years ago

  • Status changed from New to Closed
  • Branch set to master

This working now : it is possible to put a [jcom.receive model/address] into a view patcher to get the effective model/address on which the view is binding.

Also available in: Atom PDF