phiol

Is there a way to get the same info (varname) about an object (as diplayed in the bottom left of the screen).

The simple reason is that I've create many objects using the [script newdefault ] w. [thispatcher]

and want know which is which when I click on them.

Again, is there an object that exists, to give you what appears in the lower left of the screen. I,ve search the max database objects.

I thought maybe it would be faster w. this forum.

The simple reason is that I've create many objects using the [script newdefault  ] w. [thispatcher]
and want know which is which when I click on them. 

Again, is there an object that exists, to give you what appears in the lower left of the screen. I,ve search the max database objects. 

I thought maybe it would be faster w. this forum. 

object-var-name

> Is there a way to get the same info (varname) about an object (as

> diplayed in the bottom left of the screen).

Do you mean the hints when hoovering over inlets/outlets?

You can set them with the inspector of the inlet/outlet...

In my copy of max they would always show the name of the object as well...

phil schrieb:
> Is there a way to get the same info (varname) about an object (as
> diplayed in the bottom left of the screen).

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


>In my copy of max they would always show the name of the object as well...

Yes, that's exactly it, I want to get the name (

>Do you mean the hints when hoovering over inlets/outlets?

yes. Again, i want to get all that is displayed inside a [message]

or more precisely, I will parse the (customname).

So again, how do I get the info of an object. 

Something like midiparse but for objects.

>Do you mean the hints when hoovering over inlets/outlets?
yes. Again, i want to get all that is displayed inside a [message]

or more precisely, I will parse the (customname). 

So again, how do I get the info of an object. 
Something like midiparse but for objects.

> or more precisely, I will parse the (customname).

phil schrieb:
> or more precisely, I will parse the (customname).

You probably need to do it yourself in javascript...

You can get a list of all objects and their position, then look at your 

What do you want to do with it? If its in a fixed patch, you usually 

know where what is. You could also capture your scripting in a coll, if 

its about scripted objects, and just compare to the mouse position...

phil schrieb:
> I'm on max 4.6 
>
> Do you know of an equivalency?

You can get a list of all objects and their position, then look at your 
mouse position...

What do you want to do with it? If its in a fixed patch, you usually 
know where what is. You could also capture your scripting in a coll, if 
its about scripted objects, and just compare to the mouse position...

I think I know where Phil is coming from and I have wished for the same feature in the past.

Sometimes when creating a ton of named objects and it's hard to keep track if you are patching with a lot of [pvar]'s and [pattr @bindto scriptname]'s and doing lots of scripting with [thispatcher] or js or whatever. In this case I sometimes just start adding comments as notes to myself, or get in the habit of double checking the script name in the inspector (this got a lot easier in Max 5).

In these situations it would be nice if when you move the mouse over an object, it could show you the scripting name along with the usual details about the object. In Max 5 I guess it makes the most sense for this to go in the clue window. Similarly it would be cool if it showed pattr paths when applicable.

>You probably need to do it yourself in javascript...

Unfortunately, I don,t know javascript at this moment.

right now , mw and a friend of mine are working on live audio/visual capture.

The patch I did stacks either [waveform~] or [imovie] one upon another, so that we can visually see the samples that we take. (made it so that he can see his video capture by just putting his mouse over it /cliking and moving.< it will show him his entire capture in loop.

Anyways , the way it works is that it initially stacks the first 10 captures, then you have the option to select the captures you want to replace. 5 , 2 ,9 etc.

That's why I wanted to know if it was possible to see the object's pedigree , that this would trigger the position of the next object to be created.

simple create a [message] w. name "video1" that will be placed beside each respective objects. Then , when you want to change that sample or capture , click on the [message] located beside it's object, and that you trigger the next object to be created.

In the end, I just thought it would be way more simple to have a [hover] equivalency so there be a lot less patching/scripting to do. Basically, just more efficiant and simple.

If you really want to know...
right now , mw and a friend of mine are working on  live audio/visual capture. 

The patch I did stacks either [waveform~] or [imovie] one upon another, so that we can visually see the samples that we take. (made it so that he can see his video capture by just putting his mouse over it /cliking and moving.< it will show him his entire capture in loop. 

Anyways , the way it works is that it initially stacks the first 10 captures, then you have the option to select the captures you want to replace. 5 , 2 ,9 etc. 

That's why I wanted to know if it was possible to see the object's pedigree , that this would trigger the position of the next object to be created. 

Of course, I know how to solve this;
simple create a [message] w. name "video1" that will be placed beside each respective objects. Then , when you want to change that sample or capture , click on the [message] located beside it's object, and that you trigger the next object to be created. 

Of course , all of this w. [thispatcher] 

In the end, I just thought it would be way more simple to have a [hover] equivalency so there be a lot less patching/scripting to do. Basically, just more efficiant and simple. 

>You could also capture your scripting in a coll, if

I am a bit unclear on how to do this. (I never us coll)

I have had a look into it (because of your mention) but am still unclear.

>You could also capture your scripting in a coll, if
its about scripted objects, and just compare to the mouse position...

I have had a look into it (because of your mention) but am still unclear. 

> In these situations it would be nice if when you move the mouse over

> an object, it could show you the scripting name along with the usual

But Max did that already in Max 4.? if you hover over an inlet or outlet 

in patching mode, it would tell you the scripting name as well. Of 

course if you switched of the hints, you'd miss it... ;-)

> Of course , all of this w. [thispatcher]

> In the end, I just thought it would be way more simple to have a

> [hover] equivalency so there be a lot less patching/scripting to do.

> Basically, just more efficiant and simple.

If you create the objects by scripting, you could also place them at 

different locations instead of stacking them. I usually have a sprintf 

anyway, and one of the dimensions could be %i instead of a fixed 

number... That way you can differentiate by position...

But I am not sure if I understood that correctly...

Adam Murray schrieb:
> In these situations it would be nice if when you move the mouse over
> an object, it could show you the scripting name along with the usual
> details about the object. 

But Max did that already in Max 4.? if you hover over an inlet or outlet 
in patching mode, it would tell you the scripting name as well. Of 
course if you switched of the hints, you'd miss it... ;-)

phil schrieb:
 > Of course , all of this w. [thispatcher]
 >
 > In the end, I just thought it would be way more simple to have a
 > [hover] equivalency so there be a lot less patching/scripting to do.
 > Basically, just more efficiant and simple.
 >
 > What do you think?

If you create the objects by scripting, you could also place them at 
different locations instead of stacking them. I usually have a sprintf 
anyway, and one of the dimensions could be %i instead of a fixed 
number... That way you can differentiate by position...
But I am not sure if I understood that correctly...

object var name