Am 22.02.2013 21:36, schrieb Arsenij Solovjev:
2013/2/22 Stefan Rossbach <srossb...@arcor.de <mailto:srossb...@arcor.de>>
Am 22.02.2013 17:49, schrieb Arsenij Solovjev:
Also forgot to add to mildly irritating things:
c) The Apperance Preference Page only says "Please choose your
favorite color", the user is never informed what effect this has.
As it stands, he/she might as well think we'd like to get to know
their personality better.
At least you are complaining about your own code :P
Credit where credit is due ;)
2013/2/22 Arsenij Solovjev <xeper...@gmail.com
<mailto:xeper...@gmail.com>>
Hallo dear devs,
There is one critical bug, no regressions and a few mildly
irritating things.
The critical bug:
a) Session-6 doesn't work: the host always gets his favorite
color, no matter which
color it had in a previous session with the same contact.
Session-6 is not implemented and will be part of the next release.
Franz has not answered my
email yet regarding Session-6
We were all under a different impression. Session-6 was supposed to be
one of the cornerstones
of this release. If your email was about having it work for only 2
participants
then I can say that he agrees. Miscommunication took place?
Franz told me that it should be mandantory that if two users join the
session, they will always get
the same color. So I ask Franz the following:
Hi Franz,
*censored*
Es stellt sich halt die Frage, wie oft unterschiedliche Personen
zusammenen Arbeiten. Bei fast gleicher Konstellation würde es nämlich
ausreichen,
wenn die betroffenen Personen einfach ihre Farben voreinstellen.
Wenn es dir reicht implementier ich das nur für 2 Benutzer, da dürfen
dann noch einmal andere ran und den Algorithmus überarbeiten.
I have never received a reply, so either I never received the response
or he accepted the current solution for now.
A few mildly irritating things:
a) The colors in the SUC change to the Session colors as
soon as a session is started,
and revert to the old grey and cyan (which don't look
pleasant anyway) when the session ends.
Working as intended
We know it was never a requirement. A little irritating, though, so
we thought it's worth a mention here
The best solution would be to not coloring the SUC at all.
b) We couldn't reproduce bug #3458952 on the old release.
Both the new and the old release displayed the same kind of
behaviour:
- A invited B and B accepted and chose a project location.
- While B was modifying a shared file the whole time, a
session negotiation is started with C
- B got restricted to read-only, and couldn't regain
permissions (The grant write-access context menu item, was
greyed out on the host's side)
This should not happen oO
BR,
Arsenij and the test team
Log files ?!
Will have to look them up if I can.
Can be found (depending on the configuration) for STF launch
$yourworkspacedirectory/.metadata/logs ... for normal mode
$yourworkspacedirectory/.metadata/SarosLogs and please provide the
Eclipse $yourworkspacedirectory/.metadata/log file too.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net <mailto:DPP-Devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/dpp-devel
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel
