[visionegg] Re: Restrictions for choosing TCP names?
- From: Andrew Straw <astraw@xxxxxxxxxxx>
- To: visionegg@xxxxxxxxxxxxx
- Date: Wed, 21 Nov 2007 09:53:06 -0800
Hi Kaspar,
I'm not sure what the issue is -- the gratingTCP demo has a controller
with tcp_name "orient", and it works (I just checked), so I guess the
issue lies with your program.
Kaspar Müller wrote:
Can anyone help me with the TCPController-Class?
I found the strange behaviour, that when I want to change for example
the Orientation of the stimulus (singratings) via TCP (I use Labview to
control), I can't do it if the tcp_name for the orientation-controller
is set to "orient", but if I use a different tcp_name, e.g. "con" it works.
are there any restrictions for choosing tcp-names?
best, Kaspar
======================================
The Vision Egg mailing list
Archives: http://www.freelists.org/archives/visionegg
Website: http://www.visionegg.org/mailinglist.html
======================================
The Vision Egg mailing list
Archives: http://www.freelists.org/archives/visionegg
Website: http://www.visionegg.org/mailinglist.html
- References:
- [visionegg] Restrictions for choosing TCP names?
- From: Kaspar Müller
Other related posts:
- » [visionegg] Restrictions for choosing TCP names?
- » [visionegg] Re: Restrictions for choosing TCP names?
Can anyone help me with the TCPController-Class?I found the strange behaviour, that when I want to change for example the Orientation of the stimulus (singratings) via TCP (I use Labview to control), I can't do it if the tcp_name for the orientation-controller is set to "orient", but if I use a different tcp_name, e.g. "con" it works.
are there any restrictions for choosing tcp-names? best, Kaspar ====================================== The Vision Egg mailing list Archives: http://www.freelists.org/archives/visionegg Website: http://www.visionegg.org/mailinglist.html
- [visionegg] Restrictions for choosing TCP names?
- From: Kaspar Müller