-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run TLE update in its own thread #43
Comments
Alternatively, we could use async calls in GIO. Local files could be specified using file:// and treated together with remote files. This could possibly reduce the amount of code we have. |
While looking at the code, it doesn't seem to have a way to set a specific proxy for I've asked about proxy on a forum and been suggested to use libsoup. Are you OK to add libsoup to dependencies? This discussion might be interesting to read. |
Thanks for the heads-up. To be honest, I have been thinking about ditching the proxy setting anyway since I don't think anybody uses it (obviously, I can't know for sure, but I have never been able to test it). I don't like the idea of adding a new dependency for this purpose. The advantage of using functions in Glib is that we could get rid of the libcurl dependency, but not if we would be replacing it with a new dependency :) |
Do you want to remove the proxy setting with v2.4? Would you mind creating an issue for it? |
I have created an issue for it (#243) and I have sent out inquiries to see if anyone needs support for proxy servers. |
Currently the TLE update function runs in the main GUI thread and this can cause the GUI to freeze. TLE update should run in its own thread and report progress and status through appropriate channels.
The text was updated successfully, but these errors were encountered: