I finally got QuteCsound-d-py.exe built and it runs and it renders
some of the demos. I like the integration of examples. This obviously
includes PythonQt which I built by hard-coding various libs and paths
in the .prf and .pro files.

There is however a problem that I and possibly others will find
annoying. That is in the Python integration, sys.argv has no meaning.
I am in the habit of using sys.argv[0], which contains the path of the
Python script that is running, as a base from which to derive the
names of all other files in my projects.

Is this the case if I build without PythonQt? (actually I will try
that and see). Is there some other way of obtaining the path of the
script that is running from Python?

Regards,
Mike

-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Oh, I see that there is a workaround, just run the Python script in
the console. That works fine.

Still, I would prefer to run in the QuteCsound environment as it may
be useful to use the widgets etc. and to script them in my pieces, so
let me know if you have any answers to my questions.

Great work here! Just keeps getting better. Should have a release soon.

Regards,
Mike

On Tue, Jan 25, 2011 at 8:36 PM, Michael Gogins
 wrote:
> I finally got QuteCsound-d-py.exe built and it runs and it renders
> some of the demos. I like the integration of examples. This obviously
> includes PythonQt which I built by hard-coding various libs and paths
> in the .prf and .pro files.
>
> There is however a problem that I and possibly others will find
> annoying. That is in the Python integration, sys.argv has no meaning.
> I am in the habit of using sys.argv[0], which contains the path of the
> Python script that is running, as a base from which to derive the
> names of all other files in my projects.
>
> Is this the case if I build without PythonQt? (actually I will try
> that and see). Is there some other way of obtaining the path of the
> script that is running from Python?
>
> Regards,
> Mike
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi,

I'm not really sure how this could be done, as to access the widgets,
the way I've done it is have an object for the QuteCsound API in the
running interpreter, and then execute the scripts within the
interpreter, so in effect there are no arguments...

Cheers,
Andres

On Wed, Jan 26, 2011 at 1:41 AM, Michael Gogins
 wrote:
> Oh, I see that there is a workaround, just run the Python script in
> the console. That works fine.
>
> Still, I would prefer to run in the QuteCsound environment as it may
> be useful to use the widgets etc. and to script them in my pieces, so
> let me know if you have any answers to my questions.
>
> Great work here! Just keeps getting better. Should have a release soon.
>
> Regards,
> Mike
>
> On Tue, Jan 25, 2011 at 8:36 PM, Michael Gogins
>  wrote:
>> I finally got QuteCsound-d-py.exe built and it runs and it renders
>> some of the demos. I like the integration of examples. This obviously
>> includes PythonQt which I built by hard-coding various libs and paths
>> in the .prf and .pro files.
>>
>> There is however a problem that I and possibly others will find
>> annoying. That is in the Python integration, sys.argv has no meaning.
>> I am in the habit of using sys.argv[0], which contains the path of the
>> Python script that is running, as a base from which to derive the
>> names of all other files in my projects.
>>
>> Is this the case if I build without PythonQt? (actually I will try
>> that and see). Is there some other way of obtaining the path of the
>> script that is running from Python?
>>
>> Regards,
>> Mike
>>
>> --
>> Michael Gogins
>> Irreducible Productions
>> http://www.michael-gogins.com
>> Michael dot Gogins at gmail dot com
>>
>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Yes, I understood you must be doing something like that. I will google
python lists for a workaround, but executing in the console is
tolerable.

Regards,
Mike

On Wed, Jan 26, 2011 at 3:20 AM, Andres Cabrera  wrote:
> Hi,
>
> I'm not really sure how this could be done, as to access the widgets,
> the way I've done it is have an object for the QuteCsound API in the
> running interpreter, and then execute the scripts within the
> interpreter, so in effect there are no arguments...
>
> Cheers,
> Andres
>
> On Wed, Jan 26, 2011 at 1:41 AM, Michael Gogins
>  wrote:
>> Oh, I see that there is a workaround, just run the Python script in
>> the console. That works fine.
>>
>> Still, I would prefer to run in the QuteCsound environment as it may
>> be useful to use the widgets etc. and to script them in my pieces, so
>> let me know if you have any answers to my questions.
>>
>> Great work here! Just keeps getting better. Should have a release soon.
>>
>> Regards,
>> Mike
>>
>> On Tue, Jan 25, 2011 at 8:36 PM, Michael Gogins
>>  wrote:
>>> I finally got QuteCsound-d-py.exe built and it runs and it renders
>>> some of the demos. I like the integration of examples. This obviously
>>> includes PythonQt which I built by hard-coding various libs and paths
>>> in the .prf and .pro files.
>>>
>>> There is however a problem that I and possibly others will find
>>> annoying. That is in the Python integration, sys.argv has no meaning.
>>> I am in the habit of using sys.argv[0], which contains the path of the
>>> Python script that is running, as a base from which to derive the
>>> names of all other files in my projects.
>>>
>>> Is this the case if I build without PythonQt? (actually I will try
>>> that and see). Is there some other way of obtaining the path of the
>>> script that is running from Python?
>>>
>>> Regards,
>>> Mike
>>>
>>> --
>>> Michael Gogins
>>> Irreducible Productions
>>> http://www.michael-gogins.com
>>> Michael dot Gogins at gmail dot com
>>>
>>
>>
>>
>> --
>> Michael Gogins
>> Irreducible Productions
>> http://www.michael-gogins.com
>> Michael dot Gogins at gmail dot com
>>
>> ------------------------------------------------------------------------------
>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
>> Finally, a world-class log management solution at an even better price-free!
>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
>> February 28th, so secure your free ArcSight Logger TODAY!
>> http://p.sf.net/sfu/arcsight-sfd2d
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net