5: a small list of things

May 3, 2008 at 9:39pm

5: a small list of things

(below refers to macosx 10.5 and max 5.0.1 with all options of the Options menu enabled)

1. instantiate new jweb
2. connect readfile message
3. read a file from disk
4. open jweb inspector and enable scrollbars
5. scrollbars won’t show until next launch of the patch

1. quit max
2. launch max
3. new patcher window
4. new object eg. notein (it’s important not to click in empty space while creating objects, otherwise this trick won’t work–instantiating should be done with ENTER)
5. new object eg. noteout
6. open inspector (cmd-i) on most recent created object (noteout)
7. if inspector opens on top of patcher window move it away
8. select other object (notein)
9. notice how inspector doesn’t update
10. after having clicked somewhere else, selecting the objects will properly update the inspector’s content.

minor inconsistencies or useful additions (I know demanding customers can really be annoying, but here I go):

The inspector window is designed to be continuously there (like the floating inspector of that other program, what was it called again) and while it can be empty when nothing is selected it cannot be opened without selecting an object.

Since the difference between a locked or unlocked patcher is visually speaking so tiny (the dots of the grid don’t help too much, showing the grid a bit too much) maybe being able to change the color of the grid to a brighter one might be one (and yet another) option.

alt-clicking on a bogus object doesn’t bring up bogus.help but instead max will try to find the help file of what the bogus contains (eg no help found for poobah). Also it appears that changing the default color for a bogus object doesn’t have anymore effect, although it did have once, I think. Anyhow the background color for a single bogus object through it’s inspector does not coincide with the created default for bogus, but with the default of a regular object. Changing that color doesn’t update the object. (I’m so stuck now).

Initially I wasn’t able to decide wether I wanted assistance because of the nervous flickering effect it has, but it is too useful to abandon it. A slight delay (option? help!) would overcome this, and the whole experience would be enhanced if the area which starts assistance (the size of the inlet or outlet itself) would upon starting grow one ore two pixels on either side so that the pointer doesn’t have to be aimed at a relatively small area (crossing a relatively small area will start it, coming to a halt in a relatively bigger area will continue it). The same holds for having the messages and actions menu pop up.

With a maximized window the assistance of the toolbar options is offscreen.

In the scripting example of thispatcher, the scripted connection doesn’t appear the first, but only the second time, after a disconnect.

The fact that autocompletion works only with adding characters and not with removing them can be tricky at times.

The ENTER key does instantiate objects but for messages or comments it’s being interpreted as a new line a la RETURN. Extra click required (ok, shift+enter will also work).

Upon creating an object or a patch cord, it is selected (perfect) but cmd-clicking in empty space thereafter won’t lock the patcher window but will deselect what was created. Only the second time will it lock (extra click required).

(Some of the things mentioned here are from the perspective of achieving the laziest as possible working method, in order to avoid physical damage, where every extra click or mouse movement is considered a useless effort. I normally work with a tablet (which isnt’ too accurate, sometimes when clicking the pointer moves a pixel) and try to avoid bringing my writing hand to the keyboard a much as possible for reasons of speed.)

Here I’ll stop, before I overdo it.

#37518
May 3, 2008 at 10:25pm

On May 3, 2008, at 2:39 PM, jvkr wrote:
> Since the difference between a locked or unlocked patcher is
> visually speaking so tiny (the dots of the grid don’t help too much,
> showing the grid a bit too much) maybe being able to change the
> color of the grid to a brighter one might be one (and yet another)
> option.

Have you noticed the preference for “Unlocked Patcher Background” in
Object defaults? This addresses making the edit mode visually distinct
from locked mode.

-C

Chris Muir
cbm@well.com

http://www.xfade.com

#129698
May 4, 2008 at 6:50am

#129699
May 4, 2008 at 7:17am

>These two things are the most obvious annoying detail not related to the
>look and feel of Max 5. I sincerly lose time because of this. We learned
>how to max smoothly, and now it’s like stumbling on every step.

Also, in “All Windows Active” mode, you cant bring a window to the front by command-clicking it, like it was on Max4, you have to click on the transport bar (wich could be hidden by other windows): this slowes editing a bit, imho.

m

#129700
May 4, 2008 at 10:08am

Quote: f.e wrote on Sun, 04 May 2008 08:50

> > Upon creating an object or a patch cord, it is selected (perfect) but cmd-clicking in empty space thereafter won’t lock the patcher window but will deselect what was created. Only the second time will it lock (extra click required).
>
> These two things are the most obvious annoying detail not related to the
> look and feel of Max 5. I sincerly lose time because of this. We learned
> how to max smoothly, and now it’s like stumbling on every step.

Yes, can command-click be “lock patch” again, please?

regards,
kjg

#129701
May 4, 2008 at 12:36pm

Command-click locks my patches with and without ‘All Windows Active’
on, on my machine using Max 5.0.1.

On Sun, May 4, 2008 at 6:08 AM, Klaas-Jan Govaart wrote:

> Yes, can command-click be “lock patch” again, please?

#129702
May 4, 2008 at 2:54pm

#129703
May 5, 2008 at 12:27am

#129704
May 5, 2008 at 1:27am

Is it possible to add new columns for sort criteria in the File Browser, e.g., by Last Modified, etc.?

#129705
May 5, 2008 at 1:37am

Right-click in the header of the grid in file browser and select the
columns you want to see.

Cheers

Brad

On 4-May-08, at 7:27 PM, matt wrote:

>
> Is it possible to add new columns for sort criteria in the File
> Browser, e.g., by Last Modified, etc.?
>
>
> –
> http://www.virb.com/cebec

#129706
May 5, 2008 at 1:54am

Ah, ok, thanks, got it!

Quote: bdc wrote on Sun, 04 May 2008 19:37
—————————————————-
> Right-click in the header of the grid in file browser and select the
> columns you want to see.
>
> Cheers
>
> Brad
>
>
> On 4-May-08, at 7:27 PM, matt wrote:
>
> >
> > Is it possible to add new columns for sort criteria in the File
> > Browser, e.g., by Last Modified, etc.?
> >
> >
> > –
> > http://www.virb.com/cebec
>
>
—————————————————-

#129707
May 5, 2008 at 2:43am

Selecting a panel and changing the color makes it difficult to see what the color will be since the selection color is different from the color you happen to be choosing, i.e., the unselected color. Does this make sense?

Also, selecting a cable and changing its color seems to change one of the objects the cable is connected to, as well.

Finally, I was wondering if curve~ has had the issue fixed where the actual ‘c’ value is actually slightly positive even though the display value is ’0.000′.

#129708
May 5, 2008 at 5:27am

On May 4, 2008, at 7:43 PM, matt wrote:
> Selecting a panel and changing the color makes it difficult to see
> what the color will be since the selection color is different from
> the color you happen to be choosing, i.e., the unselected color.
> Does this make sense?

This annoyed me a little, too. I made this little patcher, which I
keep in the Extras menu, that helps a little, albeit in a slightly
intrusive manner. You need to hang a “r kuler” off of whatever you
want to modify. Then you can lock your patcher and change the color of
what ever is connected to the “r kuler.”

– Pasted Max Patch, click to expand. –

> Also, selecting a cable and changing its color seems to change one
> of the objects the cable is connected to, as well.

I can’t duplicate this one.

-C

Chris Muir
cbm@well.com

http://www.xfade.com

#129709
May 5, 2008 at 6:49am

Did you notice that while you are changing the color, the selection overlay of the object disappears? When you hide the color palette it reappears. I’m not sure why this isn’t good enough, but if it isn’t, another thing you can do is add the object to the presentation and change it in presentation mode.

David Z.

#129710
May 5, 2008 at 7:18am

On May 4, 2008, at 11:49 PM, David Zicarelli wrote:
> Did you notice that while you are changing the color, the selection
> overlay of the object disappears? When you hide the color palette it
> reappears. I’m not sure why this isn’t good enough, but if it isn’t,
> another thing you can do is add the object to the presentation and
> change it in presentation mode.

I hadn’t thought of doing this in presentation mode. That will
probably work for me just about all of the time.

The reason it doesn’t work so well for me in edit mode is basically my
own fault: I have a background color in edit that makes it hard to
make good judgements about color. It sure makes it easy to tell I’m in
edit mode, though :-)

Chris Muir
cbm@well.com

http://www.xfade.com

#129711
May 5, 2008 at 8:16am

On May 5, 2008, at 12:18 AM, Chris Muir wrote:
> I hadn’t thought of doing this in presentation mode. That will
> probably work for me just about all of the time.

I need to think about things before replying more. I have the same
self-inflicted problem with presentation mode.

My kludgey solution works for me, so I guess I’ll stick with it.

Chris Muir
cbm@well.com

http://www.xfade.com

#129712
May 5, 2008 at 8:33am

#129713
May 5, 2008 at 9:49am

f.e wrote:
> Chris, what about the ctrl-click unlock on first click ?

Oh yes, please !

Cheers.

#129714
May 5, 2008 at 12:50pm

> Chris, what about the ctrl-click unlock on first click ?

> f.e

The problem is that ctrl-click doesn’t work when an object is selected. This will be fixed for the next incremental release.

Rob

#129715
May 5, 2008 at 1:37pm

Yes you’re right. It should lock on the first click.

On Sun, May 4, 2008 at 10:54 AM, f.e

wrote:
> No. When you’re still on the newly created object, it only locks your patch
> after you’ve clicked twice. In Max 4, it was one click and it was smooth.
>
> f.e

#129716
May 5, 2008 at 6:19pm

On May 5, 2008, at 1:33 AM, f.e wrote:
> Chris, what about the ctrl-click unlock on first click ?

Why me? It’s listed as fixed in the 5.0.2 info here:

http://www.cycling74.com/version/version_5_0_2.html

“cmd+click to lock a patcher now works when objects are selected”

-C

Chris Muir
cbm@well.com

http://www.xfade.com

#129717
May 5, 2008 at 9:04pm

#129718
May 5, 2008 at 9:26pm

#129719

You must be logged in to reply to this topic.