cnc control configurability was Re: Text file description of GUI ...
Posted by
ballendo
on 2002-02-20 03:49:54 UTC
John,
Here are a few possible reasons:
Let's start with the thought that a given cnc control needs to be
consistent across its implementation. Because...
1)"Standard" windows programs do not control machines that can maim
or kill. (more below)
2) In a low cost product, either support issues need to be minimised,
or the creator has to be doing it for other than monetary reasons.
Then let's look at the fact that most of these controls are "one man"
enterprises. There's a LOT to writing a cnc control, and a LOT MORE
to writing a "decent" cnc control, even BEFORE you get to UI issues.
3)Which is more important? The ability to add/remove screen features.
Or smooth motion, effective code interpretation, and price? (A guy
working alone HAS to make these sorts of choices)
4)It's hard enough squashing bugs caused by "undocumented" features
of the OS. And supporting the variations in keyboards, graphics
displays, and ports, to name a few "trouble" areas I've seen pc-based
controls wrestle with over the years.
5) When I'm at the "other end" of the phone (or email) trying to
solve your problem (whatever it might be); I'm MILES ahead KNOWING
what your control "looks" like. Not to mention that IBM and Microsoft
BOTH have done "blind" studies which show that the
user/operator "leaves out" LOTS of pertinent details, EVEN
when "prompted" by service personnel. (Often out of a fear of it
being "their fault" if they mention that they re-configured the
whatchamajiggy).
5)Next let's realise that "windows" programming, at the hobbyist
level for cnc controls, is still in its infancy. And that a lot of
the people writing controls are NOT professional programmers; but
have been led to it by "need". (no disrespect intended. We ALL start
NOT knowing...)
Cars, boats, airplanes, table saws, stoves and machine tools; all
have "common" interfaces, and "rules" of operation. They are
dangerous items, and the consistency of their operation makes
everyone safer. and they all have "over-seeing agencies" to insure
the safety of their users.
As a control writer, I don't care if you change your word-processor,
email, gaming console, or i-net portal to suit your desires. But I DO
care if the changes you might make to my control product make it
unsafe, or hard to provide suport for. And you might not even know
that you have done so...
Having said this, I DO think that you SHOULD be able to "configure"
your control. BUT, I think control writers had better be pretty
careful what they "allow" you to do, change wise.
Lastly, I think GOOD design (and "respect" for what has come before,
whether you are incorporating it, or "launching" FROM it) eliminates
much of the NEED to make the type of UI changes you mention.
This isn't a printer; it's a machine that can maim or kill... (even
the small ones- double entendre intended)
Hope this helps.
Ballendo
Here are a few possible reasons:
Let's start with the thought that a given cnc control needs to be
consistent across its implementation. Because...
1)"Standard" windows programs do not control machines that can maim
or kill. (more below)
2) In a low cost product, either support issues need to be minimised,
or the creator has to be doing it for other than monetary reasons.
Then let's look at the fact that most of these controls are "one man"
enterprises. There's a LOT to writing a cnc control, and a LOT MORE
to writing a "decent" cnc control, even BEFORE you get to UI issues.
3)Which is more important? The ability to add/remove screen features.
Or smooth motion, effective code interpretation, and price? (A guy
working alone HAS to make these sorts of choices)
4)It's hard enough squashing bugs caused by "undocumented" features
of the OS. And supporting the variations in keyboards, graphics
displays, and ports, to name a few "trouble" areas I've seen pc-based
controls wrestle with over the years.
5) When I'm at the "other end" of the phone (or email) trying to
solve your problem (whatever it might be); I'm MILES ahead KNOWING
what your control "looks" like. Not to mention that IBM and Microsoft
BOTH have done "blind" studies which show that the
user/operator "leaves out" LOTS of pertinent details, EVEN
when "prompted" by service personnel. (Often out of a fear of it
being "their fault" if they mention that they re-configured the
whatchamajiggy).
5)Next let's realise that "windows" programming, at the hobbyist
level for cnc controls, is still in its infancy. And that a lot of
the people writing controls are NOT professional programmers; but
have been led to it by "need". (no disrespect intended. We ALL start
NOT knowing...)
Cars, boats, airplanes, table saws, stoves and machine tools; all
have "common" interfaces, and "rules" of operation. They are
dangerous items, and the consistency of their operation makes
everyone safer. and they all have "over-seeing agencies" to insure
the safety of their users.
As a control writer, I don't care if you change your word-processor,
email, gaming console, or i-net portal to suit your desires. But I DO
care if the changes you might make to my control product make it
unsafe, or hard to provide suport for. And you might not even know
that you have done so...
Having said this, I DO think that you SHOULD be able to "configure"
your control. BUT, I think control writers had better be pretty
careful what they "allow" you to do, change wise.
Lastly, I think GOOD design (and "respect" for what has come before,
whether you are incorporating it, or "launching" FROM it) eliminates
much of the NEED to make the type of UI changes you mention.
This isn't a printer; it's a machine that can maim or kill... (even
the small ones- double entendre intended)
Hope this helps.
Ballendo
--- In CAD_CAM_EDM_DRO@y..., "j.guenther" <j.guenther@v...> wrote:
> My biggest complaint with all of the CNC gui's is that I have no
choice as
> to what buttons I have on my screen. If I don't need or want a
particular
> function on the screen, why can't there be an option to remove that
function
> from the screen or place it on a secondary screen? The functions
could all
> be left in the pull down menu's but not have the buttons on the
screen if
> one chose not to have it on the screen. This is pretty much
standard
> windows programming, so why do the CNC controll programs ignore this
> capability.
>
> John Guenther
> Sterling, Virginia
>
Discussion Thread
audiomaker2000
2002-02-18 23:00:29 UTC
Text file description of GUI - controller uploaded
ballendo
2002-02-19 05:09:40 UTC
Re: Text file description of GUI - controller uploaded
audiomaker2000
2002-02-19 07:09:26 UTC
Re: Text file description of GUI - controller uploaded
Carlos Guillermo
2002-02-19 07:51:48 UTC
RE: [CAD_CAM_EDM_DRO] Re: Text file description of GUI - controller uploaded
j.guenther
2002-02-19 08:05:01 UTC
RE: [CAD_CAM_EDM_DRO] Re: Text file description of GUI - controller uploaded
ccs@m...
2002-02-19 08:22:10 UTC
Re: [CAD_CAM_EDM_DRO] Re: Text file description of GUI - controller uploaded
audiomaker2000
2002-02-19 09:13:05 UTC
Re: Text file description of GUI - controller uploaded
Carol & Jerry Jankura
2002-02-19 09:32:25 UTC
RE: [CAD_CAM_EDM_DRO] Re: Text file description of GUI - controller uploaded
Jon Elson
2002-02-19 10:55:08 UTC
Re: [CAD_CAM_EDM_DRO] Re: Text file description of GUI - controller uploaded
audiomaker2000
2002-02-19 14:26:24 UTC
Re: Text file description of GUI - controller uploaded
cadcamcenter
2002-02-19 19:56:48 UTC
Re: Text file description of GUI - controller uploaded
Chris L
2002-02-19 20:05:26 UTC
Re: [CAD_CAM_EDM_DRO] Re: Text file description of GUI - controller uploaded
Carol & Jerry Jankura
2002-02-19 20:18:47 UTC
RE: [CAD_CAM_EDM_DRO] Re: Text file description of GUI - controller uploaded
Raymond Heckert
2002-02-19 21:10:19 UTC
Re: [CAD_CAM_EDM_DRO] Re: Text file description of GUI - controller uploaded
audiomaker2000
2002-02-19 21:37:16 UTC
Re: Text file description of GUI - controller uploaded
ballendo
2002-02-20 02:45:15 UTC
multiple screens vs. one big one was Re: Text file description of GUI...
ballendo
2002-02-20 03:49:54 UTC
cnc control configurability was Re: Text file description of GUI ...
ballendo
2002-02-20 04:46:22 UTC
mice in the control was Re: Text file description of GUI - controller uploaded
Carlos Guillermo
2002-02-20 08:41:31 UTC
RE: [CAD_CAM_EDM_DRO] multiple screens vs. one big one was Re: Text file description of GUI...
audiomaker2000
2002-02-20 09:19:32 UTC
multiple screens vs. one big one was Re: Text file description of GUI...
glee@i...
2002-02-20 09:35:24 UTC
Re: [CAD_CAM_EDM_DRO] multiple screens vs. one big one was Re: Text file description of GUI...
morgtod
2002-02-20 14:43:07 UTC
Re: Text file description of GUI - controller uploaded