vining wrote: »
Ok, what if you went into another programmers PC while they were away and changed some of these parameter names around to something to obscene, personal or just plain stupid. Then watch them when they come back to program and see how long it takes them to notice the changes and figure out how it was done.
Spire_Jeff wrote: »
Spire_Jeff wrote: »
Yes, I could change the NetLinx.axi, but then I have to do it every time a new version is released ... which is only often enough for me to forget that I made changes until a few days after the upgrade which will inconveniently fall in the middle of some catastrophic failure at a job site and only serve to piss me off when I have to deal with the "old" way until I have time to make the changes again.... or AMX could make the changes once and we would not have to worry about it
As for the discussion about _ .... OneCouldJustUseCapitalsToDefineTheWordsAsWell
jjames wrote: »
ROO wrote: »
I would like to be able to use any XML editor I chose to work on a file, then in Netlinx Studio - convert the file from the generic XML format to the Netlinx XML supported format. The value would be that any editor that creates an XML format, could be used to build structures for the Netlinx. It would seem to be an easier task then creating an editor that everybody likes, and a way we could update a Netlinx XML file without fouling up the Netlinx format.
DHawthorne wrote: »
XML is a published standard, and NS should support it without conversion. I think they just need to fix this, period, forget about tools to make it happen.
annuello wrote: »
I agree. I haven't tried "non-NetLinx" XML for a few years but if I remember rightly, it doesn't like EOL characters between elements. It may not like whitespace being used to pad/indent elements either. At a bare minimum it would be nice if NetLinx could cope with these two situations. Our XML files would then become more human-readable and editable using standard text editors.
ipssheldon wrote: »
I know that this was discussed on a separate thread a while back, but I"ll mention it hear again since this is a discussion of future feature ideas. It would be great to have a way to compare 2 TPD4 files. The compare could work on several layers, compare the page and pop-up list, then within each page/pop-up, compare the buttons on each one and within each button compare the properties top to bottom and so on through the entire file.
If the TPD4 file is an XML or other text-based format encapsulated within the TPD4 file, then another approach would be a de-compiler of sorts to convert the file back to text, so that we can use third-party compare utilities (WinMerge, TortioseSVN, even Studio's compare, etc.).
This would be a life saver in my world.