Adding to the "Imports" section

Replies to This Discussion

Permalink Reply by David Rutten on March 31, 2010 at 4:57am

Hi Benjamin,

can you reach classes inside System.IO.Ports without using the Imports statement?

--
David Rutten
david@mcneel.com
Poprad, Slovakia

• ▶ Reply

Permalink Reply by castroecosta on July 22, 2011 at 8:00am

Dear Mr Rutten,

 

I have a problem similar to Benjamin's: I'm trying to create a custom VB component that takes an input real number as frequency and uses it to generate a continuous single tone.

 

I managed to use the PC beeping sound, but it has a couple of problems: I can't play two tones at the same time, if I use two or more components. Actually this is part of a bigger problem: the tones have to be playing in the backgound, since I want to be editing my GH file while the tones are playing (actually, the idea is to choose parameters in fuction of these tones).

 

Therefore, after some googling, I found that I can use DirectSound to access the sound card. But for that I need to add "Imports Microsoft.DirectX.DirectSound" to the imports in my custom VB component.

 

Any ideas on how to solve this?

Thanks in advance, and (you probably heard this a million times) congrats for a fabulous job.

 

Eduardo Castro e Costa

• ▶ Reply

Permalink Reply by David Rutten on July 22, 2011 at 10:07am

Do you know where the dll is that contains the Microsoft.DirectX.DirectSound namespace?

 

--

David Rutten

david@mcneel.com

Poprad, Slovakia

• ▶ Reply

Permalink Reply by David Rutten on July 22, 2011 at 10:13am

Darnit, there's a bug in the Imports logic, it generates uncompilable code.

 

--

David Rutten

david@mcneel.com

Poprad, Slovakia

• ▶ Reply

Permalink Reply by castroecosta on July 22, 2011 at 11:02am

Thanks for the ready reply!

 

I found some info in the link (http://pcsupport.about.com/od/findbyerrormessage/a/microsoft-direct...) about the dll, but I guess it will be irrelevant given the bug in the Imports logic, right?

 

if there is somethink I can assist you with, I'd be glad to, although my VB knowledge is very limited...

 

Best,

Eduardo

 

• ▶ Reply

Permalink Reply by David Rutten on July 22, 2011 at 1:11pm

I've fixed it already, when the next release goes out you should be able to reference additional dlls again.

 

--

David Rutten

david@mcneel.com

Poprad, Slovakia

• ▶ Reply

Permalink Reply by castroecosta on July 22, 2011 at 1:22pm

Thank you very much for your effort!

I'll be eagerly waiting for it :)

 

Best, Eduardo

• ▶ Reply

Permalink Reply by castroecosta on August 22, 2011 at 7:10am

Dear Mr. Rutten,

 

How do I reference additional dlls? I was under the impression that I had to edit the Imports section, but that is still "uneditable" (at least in 0.8.0050).

 

Thanks in advance,

Eduardo

• ▶ Reply

Permalink Reply by Luis Fraguada on August 22, 2011 at 7:12am

Eduardo, it has always been uneditable.  Right Click in the middle of the component and select 'Referenced Assemblies' to point the component to the location of the dll you want to implement.

• ▶ Reply

Permalink Reply by castroecosta on August 22, 2011 at 8:45am

Dear Mr. Fraguada,

 

thanks for the reply!

I'll give it a try then.

 

Best,

Eduardo