|
I've long since provided all the needed tech support to myself after getting a gentle nudge in the right direction. Just as I've long since reconciled my irreverent habits of using software products with stern reality. So all things non-portable can be safely thrown out of consideration.
As for the rest, me complaining? That's stretching it. It's me wondering and me suggesting. As for the app being multiplatform - oh my, I missed that, thank you. But I guess you know that some aspects of any multiplatform app are indeed platform-dependent. Like, where the configuration is stored and all that stuff. And on Windows, environment variables are not the conventional way of storing non-PATH related settings of third-party apps. I've just tried to point out that, on Windows, it's somewhat strange to stick to that way as the only way. I don't see how it depends on or could affect the app's being multiplatform.
Now, the portable mode itself isn't without its curious caveats, as I've already said. The thing is that the requirement to only use the 'calibre-portable.exe' and strictly avoid running any apps from any subdirectories of the portable installation lest the app suddenly stops being portable is one hell of a curious caveat, sorry about that, I don't care if that's also considered non-standard. And that caveat could be alleviated by putting a configuration file with all those CALIBRE_NO_DEFAULT_PROGRAMS and other settings somewhere within the portable installation directory structure, so that all the components have a common means of knowing what's going on. If this suggestion is considered a sacrilegious encroachment upon the ways of the world - fine, you're in charge. But I don't see what's so surprising in me finding something surprising.
|