Feature Request #763

automatic binding of children in the case of nested views

Added by Pascal Baltazar over 6 years ago. Updated over 4 years ago.

Status:ClosedStart date:2011-04-23
Priority:LowDue date:
Assignee:Théo de la Hogue% Done:

0%

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

Description

This is more a question than a real feature request.

in the case of a module containing modules (such as tracks in Théo's example), shouldn't the children views be binded to the relative sub-models when the parent binding is changed ?

easier to figure out with the attached patches (you need to have Théo's 0.6 overview in your search path..)

opinions, anyone ???

NestedViews.zip (1.88 KB) Pascal Baltazar, 2011-04-23 01:04 pm

NestedViewsNew.zip (2.94 KB) Pascal Baltazar, 2011-07-02 04:35 pm

History

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

  • Priority changed from Normal to Low

I would like to set the priority lower in order to observe
massive patching examples before to see if more generic
possibilities won't appears.

As I see in your example patch it seems quite easy to
avoid this missing feature and maybe you'll find other
tricks relative to /model/address binding strategy
(like declaring other /model/address.1, .2 yourself
to make a view patcher binding on more 1 model to group
ui feedback...)

Is this sounds good for you ?

#2 Updated by Pascal Baltazar over 6 years ago

maybe this is something that should work with absolute/relative addresses ?

if there is a slash at the beginning of the argument -> the view will bind to the corresponding address
if there is no slash, then it will bind to the adress below the "parent"

of course, keeping wildcards working would be great !

(currently, wildcards are working, i.e. model/address /myModel.* will bind the view to /myModel.1, /myModel.2, etc...)

#3 Updated by Pascal Baltazar over 6 years ago

a newer patcher, including the changes concerning relative adresses (no slash anymore before model/address)

#4 Updated by Théo de la Hogue about 5 years ago

having a jcom.view into a poly~ patcher is problematice : look into equalizer.view.maxpat

#5 Updated by Trond Lossius over 4 years ago

  • Status changed from New to Closed

Moved to GitHub

Also available in: Atom PDF