Cyrille:
Looks like a good start.
>>See attached screen shot.
Now, I need to make the button do things: ie: script the thing! Here is a list of what I need to achieve:
1: have X/Y/Z/A number panels display the actual coordinates for the 4 axis coordinates
>> If you load the 4axis panel as a panel in editing, and then right click one of the DRO's for
its properties, you'll see the first one has a variable name of Axis0CurPos, the next (y) has
a variable name of Axis1CurPos. These are internal variable matches so the system knows what to
put. You can use AxisnIndex or AxisnMaxVel or AxisnHomed and many others. The best way to find them
is to load a panel that has a control you wish to emulate and copy its variable name.
Each control in a panel or on the screen may also have a script attached. I do not recommend that usage,
it was an early invention and I later decided variable names are the easiest way to make a screen.
If the system doesnt have an internal match for the variable name you enter, it will look in the
general libraries to see if one exists. So generally give all DRO's Buttons etc.. a variable name,
you can then script them in many ways. A single variable name may be used on many items.
For example, you can have a button , DRO and LED all named Axis0CurPos. The DRO will show
in units the position, the LED will light up if not zero position, and the button will set current position
to a zero or 1 when pressed, depending on its toggle setting. (Thats silly of course, but its
important to understand any control may share a variable.
A variable name also can be scripted by simply adding a script of its name
in the general libraries. If a button named CurPos as a variable name is pressed, it will change
its value as a variable, and then call any script of its name. You can use GlobalSet( "MyVar" , 1) to set
a button from a script for example. Be carefull of looping where a button calls a script that sets that
button which then calls that script..ect...
So if the system knows the variable, it will handle it, if not, its expected you will from
a script.
All the rest of the questions have the same answer, simply copy the original screens variable names.
>>Some questions .
>>- Are the coordinat es something which is internal to Auggie, or something that is known by the pokeys? is pokeys >>coordinat e aware, or just a pulse engine that gets told by Auggie to pulse one way or another?
Auggie takes care of coordinates, the Pokeys uses step counts only.
>>- What did you program Auggie with? It does not look like QT, but it does not look like a visual studio C++ program >>either. Delphi? but which version?
Auggie is entirely in C++ using visual studio. Its strange look derives from the screen editing it uses, which though
a bit raw, is pretty powerful. I only had a year I wanted to devote to Auggie so the Screen editor was the first 3 months.
>>I do not know how much time you have invested in created Auggie, but it is a tremendou s amount of work that you have done here and I am very thankful of your work here!
About a year originally, a few months since I guess. I use it alot, I know its a bit raw in spots, but as a hobby
program thats free its a tremendous value. lol..
I agree with your frustrations in screen editing, I use a 43" monitor here, so you can imagine how big
it looks, but the screen editor is way overly complex, It does things Windows fights against so its
pretty complex to get it so the screen is fully zoomable to any size with all those controls. Not my
finest work but I was in a hurry. Each control is a very smart item, knows about scripting and such
and how to occupy space.. (what was I thinking...)
Art
