-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 24.11.2014 um 15:38 schrieb Oleksandr Shneyder:
I tried to launch newest client from nightly builds on Win7. I see a "waiting" pointer on the start of x2go client. But in this time I can use X2Go Client without problem and UI is responsible at that time. Did I understand you right? You have 5 sec. delay and during this delay you can't use a UI?
Sorry for not replying sooner. No, we're talking about the same cursor. "Hourglass-and-Pointer", not "Hourglass".
So while yes, one can use the UI during these 5 seconds, it nevertheless is confusing to the user. The initial reaction of the average user is "Oh, that thing's busy, I should wait". A non-technical user will not differentiate between "Hourglass-and-Pointer" and "Hourglass".
Since previous versions of X2GoClient did not exhibit this behavior, I am expecting complaints about a sudden slow startup (from non-technical users, that are not aware of the difference between those two cursor types) when I roll this thing out.
Is there no way we can avoid this? Maybe start the background processes and the reaper only when a session is in the startup phase, and not immediately when x2goclient.exe start?
- -Stefan
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUrrV9AAoJEG7d9BjNvlEZEfAH/jo1aey2FFgKji41HDYwW8ph 5KMqWj1C90brpeVoeg6bM5MyqPjyLif29DAKw4RCTDkFLyAqE1ckR4L0On+ByHaW uZOt61dnBCsmHBeMLuXOUDjLaNmou6ohBiMlDes5qc++nfkigIRzXVUid3Figco6 Kgs43ms4MEZVK9vCO7YEFyiO2UxV8L+gAyG0ashgr/jIbWIeK+Vn0KJhV9QutugU F4HKsHFJWekHtbRpWJBAOp2MpT/4iiQYltJ5n1EFrA8N19nlHrxcjPlbQ5/iV1wI dlphU3oPNKO1J1JHyxB8ubn3lVLg/Z/+1hpCruOlzJsXm+543WGsxjbPHsSAj8I= =FNzV -----END PGP SIGNATURE-----