4.0c Beta 3 (and L4 in general): Bug/complaint/suggestion: Logos 4 should check that libronixdls pro
Just as other apps check to see whether you've got them set as your default browser/MP3 player or what have you, and ask you to confirm whether you are OK with them not being the default, Logos should check upon startup whether the libronixdls protocol is set up correctly to bring up L4. If it's not, you should offer to change it (and let people say "No and don't ask me this again" if they want to). Perhaps you can tell whether L3 is even still installed or not, and if it's not, don't bother asking, just do it.
So many people have been reporting problems with this (I just pointed two more people to the registry hack fix for this today!) -- this is nuts. It's time for Logos to take care of it and not make people fix it manually.
Comments
-
[Y]
Yes Logos, please find a way to fix this without manual editing of the registry!
Prov. 15:23
0 -
[Y]
Dave
===Windows 11 & Android 13
0 -
-
Rosie Perera said:
Just as other apps check to see whether you've got them set as your default browser/MP3 player or what have you, and ask you to confirm whether you are OK with them not being the default, Logos should check upon startup whether the libronixdls protocol is set up correctly to bring up L4. If it's not, you should offer to change it (and let people say "No and don't ask me this again" if they want to). Perhaps you can tell whether L3 is even still installed or not, and if it's not, don't bother asking, just do it.
I have submitted this feature request.
0 -
thx, but I would agree with Rosie its a "fundamental" thing rather than a "feature" nicety..
Never Deprive Anyone of Hope.. It Might Be ALL They Have
0 -
Rosie Perera said:
Logos should check upon startup whether the libronixdls protocol is set up correctly to bring up L4. If it's not, you should offer to change it
We don't check at startup at prompt you, but in Logos 4.0d you can fix all the Logos 4 registry entries for all supported protocols (including libronixdls:) by running
%LOCALAPPDATA%\Logos4\Logos4.exe /register(On Windows XP, run "%USERPROFILE%\Local Settings\Application Data\Logos4\Logos4.exe" /register)
0 -
Bradley Grainger said:
We don't check at startup at prompt you, but in Logos 4.0d you can fix all the Logos 4 registry entries for all supported protocols (including libronixdls:) by running
%LOCALAPPDATA%\Logos4\Logos4.exe /register(On Windows XP, run "%USERPROFILE%\Local Settings\Application Data\Logos4\Logos4.exe" /register)
Hey, that's handy, I'll update the wiki tomorrow with that info.
Prov. 15:23
0 -
Kevin Becker said:Bradley Grainger said:
We don't check at startup at prompt you, but in Logos 4.0d you can fix all the Logos 4 registry entries for all supported protocols (including libronixdls:) by running
%LOCALAPPDATA%\Logos4\Logos4.exe /register(On Windows XP, run "%USERPROFILE%\Local Settings\Application Data\Logos4\Logos4.exe" /register)
Hey, that's handy, I'll update the wiki tomorrow with that info.
Bradley already did it:
I do think it would be good to have a separate wiki page documenting any/all command-line arguments, though, and I've asked Bradley on another thread whether there are any others we ought to know about. I do know you can pass logosref, logosres, and logos4 URIs on the command line.
0 -
Rosie Perera said:
Bradley already did it:
[:$] That's what happens when you fire off a quick post on the way to bed... This is great, though, it will greatly simplify trouble shooting hyperlink problems than having people poke through their registries... In fact I think there was a thread where Somsel couldn't get his to work... I'll go update it with this information.
Prov. 15:23
0 -
Rosie Perera said:
Bradley already did it:
I added a line for custom installations:-
Note 2: If you have a custom installation run drive:\<path>\Logos4\Logos4.exe
/registerDave
===Windows 11 & Android 13
0
