On 3/29/19 7:16 PM, Tobias Klein wrote:
I thought it may be convenient for the user to be informed about this
*before* installing a corresponding module.
Of course. That's what Xiphos' mod.mgr does, or any other UI's
equivalent. It's just a matter of whether it examines what's available
and mak
Ok, thanks. I thought it may be convenient for the user to be informed
about this *before* installing a corresponding module.
Is there a way to automatically acquire and check the .conf file without
installing the corresponding module first?
Best regards,
Tobias
On 29.03.19 08:39, Karl Klein
On 3/29/19 10:59 AM, Tobias Klein wrote:
It would be nice if the user could see that piece of information
before installing a module that requires an unlock key.
http://karl.kleinpaste.org/.../mod-mgr-w-lock.png
Xiphos' mod.mgr provides this with a "locked" column indicator, by
looking in .conf
I replied with a PocketSword screenshot, but the image was bigger than the 50k
threshold.
Would the list moderator please accept my earlier reply. Thanks.
David
Sent from ProtonMail Mobile
On Fri, Mar 29, 2019 at 15:09, Peter Von Kaehne wrote:
> There is not other than by testing against exi
There is not other than by testing against existence of a key in the conf file
Peter
> Gesendet: Freitag, 29. März 2019 um 14:59 Uhr
> Von: "Tobias Klein"
> An: "SWORD Developers' Collaboration Forum"
> Betreff: [sword-devel] Question about GerHfa2002 and locked modules in general
>
> Hi,
>
>
Hi,
I stumbled across GerHfa2002 and found that it's a locked module.
http://www.crosswire.org/sword/modules/ModInfo.jsp?modName=GerHfa2002
Is it possible through the API of InstallMgr or SWModule to detect
whether a module is locked or not?
It would be nice if the user could see that piece
