Kenneth Newby

Dear MaxMSP developers. This has been mentioned a number of times in past years and I'm going to reiterate. Dictionaries are, arguably, the most powerful data structures in Max but user interaction with them is seriously hobbled by the lack of a user interface allowing selection of individual keys in the complex hierarchy dictionaries can represent.

It will be wonderful to have some control over the display of dict.view as well as output based on mouse clicks, namely:

— control over default display, eg. state of keys, open/collapsed, messages to control key states

— response to mouse click with output similar to jit.cellblock, output dictionary reference for key clicked

With these two enhancements dict.view will become a powerful user interface object supporting a much smoother workflow when working with dictionaries.

 — control over default display, eg. state of keys, open/collapsed, messages to control key states

 — response to mouse click with output similar to jit.cellblock, output dictionary reference for key clicked

Dear MaxMSP developers. This has been mentioned a number of times in past years and I'm going to reiterate. Dictionaries are, arguably, the 

dict-view-feature-request-again

I totally would benefit from having [dict.view] display control. Each time I change some parameter, every menu unfolds and it drives me crazy – I have to have all the lists opened in a very big window all the time which defy the reason why the [dict.view] object exists – for a clear visual representation. I support your request too!

I wish for that too very much, the state of the keys, not controllable and open by default limits greatly dict.view's usage possibilities.

bumping this request, it would be really useful for things like displaying the cue list of a show etc.

Please please please,  could we have the option to

dict.view feature request (again)