James Reed wrote:
> I tried this (pyvcp.hal & pyvcp.xml) , but it kept giving me the error
> "waiting for component 'pyvcp' to become ready. I don't believe it's in
> the .xml file because I substituted a very simple file and it still
> wouldn't get past the pyvcp command. It did, however gene
I tried this (pyvcp.hal & pyvcp.xml) , but it kept giving me the error
"waiting for component 'pyvcp' to become ready. I don't believe it's in the
.xml file because I substituted a very simple file and it still wouldn't get
past the pyvcp command. It did, however generate the display.
From
On Jan 4, 2007, at 10:21 AM, [EMAIL PROTECTED] wrote:
> "James Reed" <[EMAIL PROTECTED]> wrote:
>
>> I try to be an open minded person. SInce I don't understand pyVCP
>> yet, and
>> I know a little about Qt3, I thought trying both would be a good
>> learning
>> experience. I haven't heard muc
Anders Wallin <[EMAIL PROTECTED]> wrote:
> > Oops, found a typo:
>
> there's at least one more, the line where pyvcp is called should read:
> loadusr -W pyvcp pyvcp-dro.xml
>
> (original had underscore in the filename)
Thanks for testing those files.
> John's xml has highlighted a feature
> > I've attached a pair of files, pyvcp-dro.xml and pyvcp-dro.hal, which
> > (should) implement a 3 axis DRO with one "zero" button for each axis.
>
> Oops, found a typo:
there's at least one more, the line where pyvcp is called should read:
loadusr -W pyvcp pyvcp-dro.xml
(original had unders
[EMAIL PROTECTED] wrote:
> I've attached a pair of files, pyvcp-dro.xml and pyvcp-dro.hal, which
> (should) implement a 3 axis DRO with one "zero" button for each axis.
Oops, found a typo:
> net YphaseA parport.0.pin-04-in => encoder.1.phase-A
> net YphaseB parport.0.pin-05-in => encoder.1.pha
"James Reed" <[EMAIL PROTECTED]> wrote:
> I try to be an open minded person. SInce I don't understand pyVCP yet, and
> I know a little about Qt3, I thought trying both would be a good learning
> experience. I haven't heard much about what the 2 minutes with pyVCP would
> entail, either. I think
I have made a quick "port" of qt_dro to emc2.
The Submakefile for qt_dro was not very different from what Paul suggested:
# --
emc/qt_dro/moc_qtdro.cc: emc/qt_dro/qtdro.hh
moc -o $@ $<
../bin/qtdro: emc/qt_dro/qtdro.cc em
Hi James
On Thursday 04 January 2007 00:39, James Reed wrote:
> Now, what do I do with it? I'm very new at EMC, Linux, and even Qt3, (I'm
> more familiar with Qt3 than the others, though).
You may do what ever you wish with the sources as long as you (or anyone else)
do not claim copyright a
, but that is
because of the good documentation EMC has provided.
>From: Anders Wallin <[EMAIL PROTECTED]>
>Reply-To: "Enhanced Machine Controller (EMC)"
>
>To: "Enhanced Machine Controller (EMC)"
>Subject: Re: [Emc-users] Qt3 lib and dro
>Date: Thu, 0
James Reed wrote:
> I downloaded the tarball. Thanks for your permission. Now, what do I do
> with it? I'm very new at EMC, Linux, and even Qt3, (I'm more familiar with
> Qt3 than the others, though).
what do you want to do with it ? :)
if you are new to emc, and you don't insist on QT3, the
r (EMC)"
>
>To: "emc-users@lists.sourceforge.net"
>Subject: Re: [Emc-users] Qt3 lib and dro
>Date: Wed, 3 Jan 2007 17:42:25 +
>MIME-Version: 1.0
>Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by
>bay0-mc2-f11.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3
Hi Ray
On Wednesday 03 January 2007 16:50, Ray Henry wrote:
> There is a way around it if we find that Paul successfully raises the
> proprietary flag with the work that I encouraged him to do with qt3.
You misjudge me - The point I was trying to get across was that the code in
question has NOT
The version of Paul's qt3 stuff that I have here shows the appended GPL
licensing. I'd be pleased to make a zip file of these and the two
additional files with no copyright info. Contact me off list and I'll
forward the 12k file to you.
Rayh
1 --
* Description: qemccommand.cc
* Functions to
14 matches
Mail list logo
