> I was thinking about this and I have another concern about users who
> directly modify touchy.glade: how will they incorporate changes and
> bugfixes to touchy.glade that we make in future emc2 releases?
>
> The method of inserting the contents of a second glade file into the
> first glade file is something that we should be able to make work from
> release to release.
>
> Jeff
>
Hey Jeff
Another good point.
The way I choose to code it was to have touchy look for a local copy of
the touchy glade file. If there is no local file then the standard file would
be used.
So if the standard touchy was changed in away that the user wants/must have
then they would have to copy the new touchy add their changes and save it
locally
again. or they could delete their glade file and use the new touchy.
Our releases are usually bug fixes so one wouldn't expect touchy to change much
and if we promote a safe spot for widgets then there is less problems for the
normal
user who just wants a few LEDs and buttons.
I figure if they put the effort into changing it in the first place they wont
mind
doing the upgrades and we can remind users if there is a major change in touchy.
I really feel the added freedom to customize is well worth the possible trouble.
I'm thinking more of odd ball machines needs - such as reprap machines that
want
print head temp. They could put that in the read out panel if they wanted.
I'll gladly document guide lines (do and dont's) for customizing touchy.
Thanks Chris M
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
