Improvements/Wishes for the patcher

#181

can i suggest, this topic is about what to change.... rather than how to implement it.

Id leave implementation decisions to the the implementor, we all know about HTML/CSS/XML ... and we are pretty familiar with graphical environments (including Quartz Composer)

now... if you want to get into implementation, and start developing the code, fantastic... then we will definitely be happy to discuss with you options for implementations.. not in this topic, but in the developer category or github issues.

(honestly, the reason for not doing this stuff as yet, is not, not knowing how to do it, its about time and resourcess)

#182

I second this request! I also find it hard to read and tried in vain to zoom in, pleas make it so we can :smile:

#183

4 posts were split to a new topic: Poor performance with patcher on older machine

#184

moved to separate thread...

Parameter/inlet change functions
Parameter/inlet change functions
#186

A post was merged into an existing topic: Parameter/inlet change functions

#187

A post was merged into an existing topic: Poor performance with patcher on older machine

#188

Just thinking, would an alternative execution order be possible?

My first instinct in terms of visualising signal flow would actually be top to bottom, left to right instead of left to right, top to bottom. In other words: columns instead of rows. I've been becoming increasingly aware of the importance of the execution order and have been trying to lay out my patches accordingly, but it makes it harder for me to actually keep track of what I'm doing.

Now obviously this can't and shouldn't be a global setting as it would break all existing patches, I would instead propose it be a per-patch setting so you can decide at the beginning which way round it'll be. The original execution order would obviously be the default and what gets chosen if an older patch without this flag gets imported.

Does this seem possible?

#189

I fear a patch setting for an alternative execution order will increase confusion. I do plan to address execution order, and add graph-based sorting, but this is a deep change, and importing patches requires extra care in development.
First priority in development is getting the next stable release out.

#190

I think Quartz Composer calculates execution order by working backwards from the output.

a|x

#191

For Sub-Patches and Patch/Patcher objects, how about the option to right-click on an object inlet, and have the Patcher create an Inlet object of the appropriate type for you?

Going back to the Inspector idea, this would provide a useful mechanism for reordering and labelling inlets and outlets for a Sub-Patch or Patch/Patcher.

a|x

#192

I guess there would be a right-click contextual menu, with one of the options being to do the above.
Another option in the menu might be to set a pre-scale/interpolation equation for inlet values.

a|x

#193

A useful feature for saving ressources would be a context menu option for each parameter which would make a parameter constant. If a parameter is set to constat, it then would behave similar to an attribute.

For the generated code this would mean the following. Lets take the following dsp method as example:

public: void dsp (int32buffer & outlet_out,
int param_pitch,
int param_reso){
// ...

If e.g. parameter pitch would then be set to constant, the generated code would become:

public: void dsp (int32buffer & outlet_out,
int param_reso){
static const int param_pitch = 12345;
// ...

#194

I little feature-request:
how about being able to click on the title-bar of a patch window to go to the patch file in the OS? This feature is common on OS X, and is really handy! It could be implemented as a right-click menu that dropped down from the title bar, giving the option to go to the file, and maybe also to rename it.

I must say, the more I use the Patcher, the more I discover nice little touches, like the fact that you can double-click the titlebar to toggle the window to/from fullscreen.

a|x

#195

I think this has been mentioned before, but can we please have the window position, dimensions and active tab of the object editor recalled when it is reopened....?

I've been working on some custom objects, and frankly, the workflow of using the editor is.. not great.

Every time I want to test my object, I have to

  1. Save the object (no keyboard shortcut for this)
  2. Close the Editor
  3. Reload objects

Then, when I need to go back to the code, I need to

  1. Open Object Editor with the fiddly menu
  2. Resize the Editor window
  3. Use the arrows to increment down to the tab I want

There has to be a way to speed this process up. It's maddening, currently, I have to say.

Maybe keyboard shortcuts for all these steps would help.

a|x

#196

That's normal in Windows, I didn't realise it was a special feature of the patcher?

#197

Here's a thought: how about removing the requirement to close the Object Editor window before making a patch live, but simply removing the ability to save it while the patch is live?

That would help enormously.

a|x

#198

Oh, maybe it is...

I've never noticed it before, but it must be an OS-level feature on Macs, too, because I've just realised other windows do the same thing.

How embarrassing...

a|x

#199

Whoops, I thought maybe it was a feature of the patcher on OSX. Sorry!

#200

I've now noticed that the Patch Editor window settings Are correctly recalled when you're editing an embedded patch/object, but Not when you're editing an external object, so my niggles are half fixed :wink:

a|x

#201

How about a new library file-type, to add the the existing Object and Patch types?

Code-Library / Includes

I find myself re-using C functions in multiple objects, and am now considering hiving these common functions off to a separate Utility Functions file. Since I've noticed others have done something similar, and at least one of these external libraries provide functions I'd like to use in my own objects, I thought maybe creating a mechanism for managing code-libraries might be cool.

I haven't thought through how this would work, in terms of dependency-management etc., so may be a Bad Idea.

Thoughts, anyone?

a|x