We contacted the DeskShare development team provided them with link to this forum thread. They read our discussion. They told us you are using version 4.0 which is assumed the very old version of DeskShare. They very recommended to switch to the latest version 4.8. Here is what they say:We have several newer version than version 4.0 (4.1.5, 4.4.5, 4.5, 4.6, 4.7 and 4.8).We recommend using version 4.8 on both sides (master and client). Our customer should contact us, stating his customer ID, so that we can take a look at his account and try to find the problem.We used 4.8 and didn’t reproduce the bug. We would be very happy to reproduce and fix the discussed bug using 4.0. Please drop us an e-mail to the support mail box at this web site and provide us with 4.0 download information.

We just downloaded the trial version of the latest DeskShare software and tested the latest Prof-UIS 2.88 control bars with it. All the control bar caption buttons are working OK. We tested them both on client and server computers. We also tested floating, docked and auto-hidden bars. So, this issue may be specific for your application. We need a test project reproducing this issue.

It’s worth telling that we have now reproduced the described "buggy" situation with your latest (compiled) demo app ’ProfStudio’ v2.88 by using DeskShare 4.0 Server/Client on WinXP SP2.

The standard procedure is as follows: after FOSS cleanup in local registry (just to exclude possible effects from serialization) we start a local "deskshare server" that supports bi-directional communication with the (freely available) remote "deskshare client". The authentification then is done by getting a valid PIN from the server for that specific session that will be handed out to the client for authentication. After having started ’ProfStudio’ two clearly seperated clicks on a closing ’x’ of a docked window (no doubleclick, but rather fast repeated) lead to a kind of "deadlock".

Due to the difficulties that appear when trying to explain the exact conditions that lead to the discribed behaviour, I’d rather invite you to join into a deskshare session and view the whole thing in action.

I’d suggest the following approach to conjointly reproduce the issue: you’ll download the "normal client" v4.0 from our headquarter’s website (address info by email) and we’d arrange a deskshare session on a specific date. Please, consider central european time (Germany) for dating ’cause we might be sleeping while you’re still working ;-)