Stefan Tiedje

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 

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 Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


adstatus-bug

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 

> 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 

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

> 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...


> 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 

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...

adstatus bug