If you have a problem or need to report a bug please email : support@dsprobotics.com
There are 3 sections to this support area:
DOWNLOADS: access to product manuals, support files and drivers
HELP & INFORMATION: tutorials and example files for learning or finding pre-made modules for your projects
USER FORUMS: meet with other users and exchange ideas, you can also get help and assistance here
NEW REGISTRATIONS - please contact us if you wish to register on the forum
Users are reminded of the forum rules they sign up to which prohibits any activity that violates any laws including posting material covered by copyright
Trigger Timing
14 posts
• Page 2 of 2 • 1, 2
Re: Trigger Timing
Wow, thank you very much Trog. I guess looking at the green conversion it wasn't so ridiculous as I thought. And yes, it works just fine. I'll study the Ruby "tutorial" when I have time later. Above and beyond as always... I appreciate it.
- Perfect Human Interface
- Posts: 643
- Joined: Sun Mar 10, 2013 7:32 pm
Re: Trigger Timing
You're welcome.
All schematics/modules I post are free for all to use - but a credit is always polite!
Don't stagnate, mutate to create!
Don't stagnate, mutate to create!
-
trogluddite - Posts: 1730
- Joined: Fri Oct 22, 2010 12:46 am
- Location: Yorkshire, UK
Re: Trigger Timing
TROG ... you mentioned naming of INPUTS on the RUBY module, and cautioned about punctuation and spaces in the name. Now you have me wondering ...
There have been, hmmmm .... several times I have 2 INPUT variables that have a Name and a Number.
I've been trying to keep a simple convention, using something like this:
name
name#
? Is there a way to test if a variable name [label] is not acceptable ?
There have been, hmmmm .... several times I have 2 INPUT variables that have a Name and a Number.
I've been trying to keep a simple convention, using something like this:
name
name#
? Is there a way to test if a variable name [label] is not acceptable ?
- RJHollins
- Posts: 1571
- Joined: Thu Mar 08, 2012 7:58 pm
Re: Trigger Timing
RJHollins wrote:? Is there a way to test if a variable name [label] is not acceptable ?
Something every Ruby programmer needs to know; so I've posted the answer HERE so it's easier to find.
Short version of the answer - yes, name (letters of either case) followed by digits is always acceptable. And having a convention is a fine idea - saves a hell of a lot of skipping around the code trying to remind yourself what you called things!
All schematics/modules I post are free for all to use - but a credit is always polite!
Don't stagnate, mutate to create!
Don't stagnate, mutate to create!
-
trogluddite - Posts: 1730
- Joined: Fri Oct 22, 2010 12:46 am
- Location: Yorkshire, UK
14 posts
• Page 2 of 2 • 1, 2
Who is online
Users browsing this forum: Google [Bot] and 73 guests