adstatus bug

Aug 30, 2006 at 7:40am

adstatus bug

Instead of filling the menu with a bang adstatus driver fakes the output…

Steps to reproduce bang and print that part of the help file.

Expected behaviour: refill the menu (clear, append driver1, append
driver2…) or do whats it claims to do: send out the driver names.
(I’d prefer the first variant, seems more usefull…)

This is important, to be able to choose an newly added audio interface
without restarting Max. This would work in OS X 10.4.6 and Max 4.6 for
sure…

Stefan

#P window setfont “Sans Serif” 9.;
#P window linecount 1;
#P newex 16 105 34 196617 print;
#P button 62 40 15 0;
#P number 144 63 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P user umenu 62 84 135 196647 1 64 100 0;
#X add;
#P newex 62 62 78 196617 adstatus driver;
#B color 5;
#P comment 79 41 219 196617 report list of currently available audio
drivers;
#P connect 1 0 5 0;
#P connect 1 0 2 0;
#P connect 1 1 3 0;
#P fasten 2 0 1 0 67 104 53 104 53 58 67 58;
#P connect 4 0 1 0;
#P window clipboard copycount 6;


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

#27379
Aug 30, 2006 at 3:55pm

I thought that a bang would result in the reporting of the current
state via a “set” message, but a loadbang would cause the menu to
refill? That’s what I’m getting from the PDF reference, anyway. The
way it’s laid out in the help file is sort of confusing, though. – David

On Aug 30, 2006, at 3:40 AM, Stefan Tiedje wrote:

> Instead of filling the menu with a bang adstatus driver fakes the
> output…
>
> Steps to reproduce bang and print that part of the help file.
>
> Expected behaviour: refill the menu (clear, append driver1, append
> driver2…) or do whats it claims to do: send out the driver names.
> (I’d prefer the first variant, seems more usefull…)
>
> This is important, to be able to choose an newly added audio
> interface without restarting Max. This would work in OS X 10.4.6
> and Max 4.6 for sure…

#82757
Aug 31, 2006 at 7:19pm

David Stanford wrote:
> I thought that a bang would result in the reporting of the current
> state via a “set” message, but a loadbang would cause the menu to
> refill? That’s what I’m getting from the PDF reference, anyway. The way
> it’s laid out in the help file is sort of confusing, though. – David

An I would need the promised behaviour, for sending a “set 1″ message
nobody would need the adstatus object…

Stefan


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

#82758

You must be logged in to reply to this topic.