Imho just name exe itself the same OdysseyLauncher as it in original, just when upload archive on os4depot call it OdysseyLauncherNG.lha, and in readme point out why users should use it.
Or, if you want to call exe differently then imho OdysseyLauncherNG fits well.
In any way it imho should have first two words: OdysseyLauncher, so everyone know what is that.
And we are almost full-circle back to my original idea to call it OdysseyLauncher2 ! With all the suggestions, I'm now rather stumped as to what I should call it.
Here is some first impressions on Sam440 & 4.1FE. After clicking a URL, a "launch-handler 53.38" requester pops up with «"ENV:launch-handler/URL/WWW.LH" wrong command» error. Clicking "confirm" (the only option available), a second requester appears with "Editing settings WWW.LH". There are two options : execute/cancel and clicking the former launches SYS:Prefs/URL.
The keyword is incorrectly outside the format string itself.
You have; CMDFORMAT="*"http://www.%s*"" UseExistingTab
It must be part of the format string but outside the quoted URL part, so the keyword must be between the two " " at the end, like this...
You need; CMDFORMAT= "*"http://www.%s*" UseExistingTab" At least a single space between the format and the keyword is also required.
Same goes for the other protocols, the part fed to the browser must be entirely in quotes, so the browser sees it as a single string regardless of content, and subsequently so must be the entire string for ReadItem() to get it out of the file, hence the asterisk infront of the inner quotes to make ReadItem() happy. The asterisk stops the following quote being acted upon by ReadItem().
@colinw Thanks for spotting this error! I've updated my first post & the one on AmigaWorld too.
I don't want to derail the thread, so I'd be obliged if others would refrain from commenting: This highlights one of the areas where URLOpen is rather less user-friendly than OpenURL. I don't understand why the URLOpen GUI needs to show this second set of quote marks. Not only does it lead to errors like the above, but it also then requires the ugly & unintuitive use of escaped quote marks. From my POV, it seems that both of these implementation 'features' could be hidden from the user quite easily, without any downside. Any idea if it's worth me raising an enhancement request on Bugzilla?
(In fact I have several idea on how URLOpen could be improved, mainly based on OpenURL does things.)
I agree entirely, but I didn't write the prefs editor program.
Internally, the quotation semantics are required because the functions used require them, both in the applications that use ReadArgs() to parse the commandline parameters and the prefs editor and handler to parses them.
So, if you want to do an enhancement request for prefs/URL to remove the outer quotes in the GUI, then I would have no problems simplifying what is shown to the user. (Or other enhancements).
Also I noticed URL Prefs does not always see the changes, so if I pres the "Test" button, Odyssey is not available as a choice. That happens if I change the name in "Client Name" (I changed from "ODYSSEYLAUNCHERPE" to "ODYSSEY", always paying attention to press "ENTER" and not to change to "Client Path" in this case "APPDIR:ODYSSEYLAUNCERPE"
But I already settled on the simple name of OdysseyLauncher2. No need for users to wonder what "PE" means (nor what "2001" in "OdysseyLauncher2001" means either!).
I've been busy with other things, so not actually got around to an official release yet... but something else I'm working on 'needs' OdysseyLauncher2, so I will definitely be looking to release this sooner or later...
I tried OdysseyLauncherPE but it doesn't work for me.. I followed the instructions but, for example, when i try to open a link in a mail (I use SimpleMail) a requester pops up and tell me : "Insert disc Odyssey"http:" Process 300: "Background CLI", if i choose 'Cancel' another requester pops up and tell me: "Insert disc APPDIR" Process 300 "Background CLI"
However, this is (unfortunately) yet more evidence that URL Prefs could be more user-friendly :(
yes, you are right. For example let's say there are 5 entries for each tab (excluding the "mail" tab), if you have an entry in the first (or it could be any other) tab named "odysseylauncherpe" and on another tab it's named "Odyssey" then the "test" button will omit any entry for "odyssey" as will any chooser launched by an external App.
It should at least display a warning or information that the setting is wrong.
yes, you are right. For example let's say there are 5 entries for each tab (excluding the "mail" tab), if you have an entry in the first (or it could be any other) tab named "odysseylauncherpe" and on another tab it's named "Odyssey" then the "test" button will omit any entry for "odyssey" as will any chooser launched by an external App.
I'm afraid that I don't understand the problem you are trying to describe. What do you mean by "will omit"? What should happen, compared to what actually happens? (Possibly I could create an OS4 bug report, if I understood.)
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
)