Closed elandorr closed 2 years ago
Hi @elandorr thanks for your feedback!
dual monitor support: I implemented the feature, so that the assisted can choose if he/she/it wants to share only the primary (= new default) or all screens. This feature is already available on the edge channel of the snap release and on the ppa nightly builds. The other channels/plattforms will have to wait until the upcoming release Ballsy Beaver V
(11.0.5) is published.
auto-reconnect: On bad connections, there are several settings, that can improve the situation:
Screen capture
Gray levels
- it's surprising how many details are still visible with just 16 or even 8 scales!Tick
to 300 ms or higherCompression
XZ
instead of ZIP
It would be rather tricky to implement a reliable auto-reconnect feature, which doesn't brute force the assistant ;)
The current assistant.jar doesn't open the assistant interface: you're right, I put the wrong Main-Class
in the MANIFEST.MF
of the current relase!
Some background: Since Ballsy Beaver III
(v11.0.3), the dayon_assisted.jar
adjusts the Windows UAC settings (see #42).
As this functionality depends on some library (jna and jna-platform) in order to access the Windows registry, the dayon_assisted.jar
now bigger than the dedicated dayon_assistant.jar
, which doesn't have/need this functionality.
Since version 11.0.5, there is an extra button to bring up the UAC settings dialogue on the assisted gui. So the settings can be easily adjusted manually.
Sending the clipboard to the assisted didn't work here, from did: Could you please provide further details? OS and Dayon version and release channel (store/snap/installer/quick-launch/jar) of the assisted and the assistant?
Set custom token/ip servers without rebuild: Implemented in version 11.0.5.
How about just using SSH tunnels: This would require a rather bigger refactoring. In its origin, Dayon! used to support Java Web Start
, included a Jetty web server
and was communicating unencrypted over http.I rather doubt the effort would really result in much sturdier connections.
The exes don't like the current openjdk jre v17: Yes, that's caused by an open issue @ launch4j: https://sourceforge.net/p/launch4j/bugs/218/ But hey, who needs JAVA 17? It's only supported until September 2029 - while JAVA 8 support ends in December 2030 ;)
Thanks for your feedback and suggestions, they're really appreciated!
@elandorr I just updated the dayon_assisted.jar
with the correct main class.
md5sum of the fixed version is c515c01c52bb8546f47d8a326e75166f
, the old was 0f71048a523849135f6f98b3a0f069ce
Hi, and thank you for this project! It's nice to have a private alternative to the giant corps. Punching through NAT by just hosting it yourself is nice (well, unless you're on cgnat). And it means one less thing to deal with for the other side. A few suggestions and a small bug:
-cp .\dayon_assistant.jar mpo.dayon.assistant.AssistantRunner
. The smaller file includes apparently both?Thanks again for your efforts and have a nice one!