Copperlan Manager: possible bug on German (Swiss) OS ?

[plugout]

Hi there. Fist congratulations for this really great concept. I’m using MIDI from the begin of this standard and the flexibility that you give us with this piece of software is what we are waiting for tens of years.
So this is my problem: after the installation ( V1.0 build 4) and restart, I can’t work the software because I simply can’t close the “did you know Tip 1” screen when starting Copperlan Manager. Tried on iMac, MacPro, Macbook Pro (all snow leopard) and PC Win7/32 all with German (Swiss) OS.
Did I a stupid fault or is there an other trick? Any suggestions?
Thanks for your help.

[Copperdav]

Hello plugout,

We had this problem with a previous version. It is now fixed.
Could you please download the latest files on http://www.copperlan.org and reinstall it.
It should work.

Please let us know.

Thank you
Copperdav

[plugout]

Thank you Copperdave
but the download for the differtt ssystems was yesterday evening / this morning and I had no previous installation.

best regards

plugout

[Copperdav]

Hello

It seems that on certain computer the tips window freeze.
We will update a new manager as soon as possible. Probably tomorrow morning.

Sorry
Copperdav

[CopperPhil]

Hi plugout,

I just published an update of the CopperLan Manager. So you just have to launch this application and it would suggest you to download and install the new version.

Sorry for the inconvenience...

/Phil

[hmertens]

Hello,

I have the exact same problem.
I've downloaded the latest version and I can't close the "Did you know" window.

I'm on Mac OS X Lion 10.7.2

Thanks

Hugues Mertens

[Copperhead]

I have the exact same problem.
I've downloaded the latest version and I can't close the "Did you know" window.
I'm on Mac OS X Lion 10.7.2
Thanks
Hugues Mertens

Have you tried restarting the CopperLan Manager application?
If it goes on as it should, you'll be asked to accept an auto-update.
After this is done it should be OK.
If not, we'll find another way to help you.

The fix to this problem will be in the next package update.