Okay the issue I'm having is that DcuHelper can only point you to the website or point to DcUpdater, but not the update file itself directly, ie the button points to the WebPage xml element.
What if I want to make the update available in app but not want people to find it from the website? Then people would be forced to install DcUpdater in order to get to the executable.
So the ability to set the 'destination' of that first button in DcuHelper would be appreciated, by setting it in the .dcupdate file.
I can think of 3 options, if you wish to address the issue:
* dcupdate option DcuHelperUpdateUrl that specifies either UpdateFile or WebPage as its value to choose from (as both the WebPage and the UpdateFile are already in the file) OR
This is the elegenat solution. In this case a new element would be added called DcuHelperUpdateUrl which would specifify the other element whose value should be used, so for the developer they could specify:
You would then reuse the UpdateFile|webPage value as the destination for the button.
* a dcupdate or versionxml option that specifies DcuHelperUpdateUrl that points to an http address or a website thats get loaded in the browser.
This is the easiest conceptually and the most flexible, simply specifiy a string instead (but that string is probably already specified in either the WebPage or UpdateFile elements.)
* use the webpage element as a url that can contain either html/binaries
I could abuse the WebPage element that already exists and point that to the location of the update, but that will probably introduce unintended consequences.
And your suggestion is a fourth one, where you add another button but that would make the interface more complex.