![]() I can add an admin check that closes the app rather than messing up the configuration by trying (and failing) to move things but launching anyway. I haven't tested this though as I am yet to be able to download a file! I presume this is because I'm still a Soulseek 'n00b' (!) rather than any fault of the app Always stuck in the queue. No crashes though!)Įven using the config files, the recent file list is still in the registry but I can wipe it before launch if the drive letter has changed (better to lose it than for it to point to files that aren't there anymore?). I can replace all drive letters in these files so it's all PAF compatible but no path replacement is possible (similar problem to EAC, the files look good but Soulseek won't recognise them and they are corrupt on exit. Unfortunately, these are stored in "AllUsers\AppData" so admin would be required as I can't see any way to redirect them. Soulseek makes it possible to disable writing the configuration to the registry and use (binary) config files instead. I can convert each *path* to hex and put it straight into the registry no problem but Soulseek won't recognise it without further formatting which I can't figure out. Even if I could do that, I will run into the next hurdle. Maybe I could read from reg, convert to string, write to ini, replace in file, read from ini, convert to hex, write to reg, I don't know (you get the idea!). Also would be cool to have system's qt open/save dialog style as it used to, if it's possible, as well as system theme etc.All the paths in the registry are in hex so updating *drives* will be difficult/impossible.Qt.network.ssl: Incompatible version of OpenSSL Qt.network.ssl: QSslSocket: cannot call unresolved function SSLeay Qt.network.ssl: QSslSocket: cannot resolve SSLeay_version Qt.network.ssl: QSslSocket: cannot resolve SSLeay Qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf Qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf Qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain Qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method Qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method Qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method Qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method Qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index Qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings Qt.network.ssl: QSslSocket: cannot resolve SSL_library_init Qt.network.ssl: QSslSocket: cannot resolve sk_value Qt.network.ssl: QSslSocket: cannot resolve sk_pop_free Qt.network.ssl: QSslSocket: cannot resolve sk_num Qt.network.ssl: QSslSocket: cannot resolve sk_free Qt.network.ssl: QSslSocket: cannot resolve sk_push Qt.network.ssl: QSslSocket: cannot resolve sk_new_null Qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_init ![]() Qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup Qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings Qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback Qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback Qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks Manjaro KDE stable here, stdout, not sure how bad that is, but worth mention: 1 on Close / Minimize to tray, just like qBittorrent or please use good old double quotes for all paths (cd / rm / mkdir etc), some of us build in non-default locations which may have space in path and anyway it's just a good tone to quote path for safety ) ![]()
0 Comments
Leave a Reply. |