Thanks for the good news.
Forgot to mention that my PDFs are coming out just fine. However, since there is a repetitive export feature, there doesnt seem to be any way to specify the output directory. Also, as with other like systems, the ability to parameterize the output filename and directory would be appropriate. It currently seems to put it in the files folder, and I suspect overwrite the last version. Not good for history and archiving, especially when you need to reference the archived PDF for an old object, or to see what it used to do. Axis Camera FTP output is a good example of how it can be parameterized. That way you can direct archive PDF output to:
Also, need a manual Tool to 'Export All Maps' to PDF. Since this is the only real way to save yourself from losing data without having to recreate the entire system from the XML file, its handy to export the PDF as a backup.
While I'm thinking about this, the behavior of default labels is either unstable or having trouble. If you put a 'template' label in the map settings for lets say for CPE, and then you also add APs to the map, I have had some trouble with the labels on some devices reverting back to a previous version. There seems to be a difference between a device that is added with custom label variables, and the default map setting variables. If the device has a custom label, it either reverts, possibly depending on device type, or it doesnt change when the 'master' map setting device device label is changed. Just need it to be consistent. I have seen some of my devices' labels change when changing the master map setting device label text, but it seems that the devices added later with a different set of label variables dont change, even if you want them to.
I know this is probably by design for obvious reasons, but there is a very important development concept missing.
Bottom Line Scenario:
If you have experimented around and used some great SNMP oids to create a very functional label, you would want to put that into the 'master' map setting label text box. This of course is after you have created a bunch of other similiar devices that have 'old' labels that were present in the master map setting device label. If you then change the master, if I am not mistaken, it just seems to change only the original devices created, not the newer objects with the better custom label. Thus, the only way to solve this without total re-creation, would be to create a new map, put the new and better label in it and 'copy and paste the devices from the old map. You would then hope it would allow mass update to 'all' devices on the new map. Alternatively, checkbox for tagging the objects for 'mass change' or 'update with master label' might solve the problem. Nevertheless, see how this actually ties into Cut, Copy and Paste?
Also, other components of the system, like startup map, the default output directory for a manual export of 'Tools'-Export PDF should be configurable in some 'preferences' section. Currently it always starts at someplace like the Desktop. Another instance of too many mouse clicks for repetitive operations.
BTW, the web server is still very unstable. Hit or miss if continually runs. Not yet a problem, but unclear as to why it takes so long to come up after restarting the Dude, and why it isnt reliable. However, I have found one reason it does fail. I use remote desktop to access the server its running on. I finally correlated the remote deskto access to the subsequent failure of the web server. Solved that by doing all development with the remote client. Sadly, the record for continuous operation is only about 30 hours. That was with intentionally not using RDP on the server machine. Machine is a Dell 2850 dual-Xeon, 2GB RAM, 2K3 and Dude is only application running on machine, and I am only one accessing Dude, so that was a controlled test. Only thing I can think of is it is not SP2. I want to be in front of machine when I perform that upgrade. Think that could affect the web server? BTW, no IIS installed on machine either. Trying to run very clean environment for stability testing.
Sorry to be so verbose, but spend a lot of hours in Dude development. Every time-saving improvement is greatly appreciated.
Thanks in advance, and the good work is greatly appreciated.