Just now I released version 1.4.0 of Simidude, the cross platform network clipboard and drag & drop utility.
I have added quite some features to it, for a complete list of new niceness please look here.
The problems with the Windows 7 update installer are gone as well.
Grab the latest release from our download site and tell me what you think!
Have a great day,
Torsten.
These are the release notes for version 1.4.0 of the cross platform network clipboard Simidude.
Version 1.4.0 adds quite a list of new features that will make your use of Simidude more effective and fun:
- Feature: Simidude on Windows (32-bit) and Linux now supports global hotkeys to bring the application to front or to activate the latest Simidude entry into the clipboard. On Windows (32-bit) it does not just activate the latest entry but will actually paste the entry into the active application.
- Feature: You can now enable an option to show a balloon tooltip near the tray icon whenever a new entry arrives in Simidude.
- Feature: You can now enable an option to automatically activate a new arriving Simidude entry. Please note that the entry is only activated when it is inserted top of the list of entries.
- Feature: Another new option is to let Simidude automatically download remote files or directories.
- Feature: The user manual is now included with each Simidude distribution.
- Feature: When an item arrives in Simidude for a second time, the item is moved from it’s current position in the list to the top. That makes it much easier to refind entries if the list is long.
This version is recommended for all users.
As always if you have any feature requests please let me know- loud and clear.
by tuhlmann on September 16, 2009 Posted in IT
After I received an update for my UMTS modem driver to finally work with Snow Leopard I again decided to update my MacBook Pro to Snowy.
After getting that system up to speed again I continued working on Simidude- I’m about to integrate global hotkey support- at least on Windows and Linux for now.
Firing up Eclipse, editing a bit and launching Simidude brought me this error:
java.lang.UnsatisfiedLinkError: Cannot load 32-bit SWT libraries on 64-bit JVM
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:182)
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:159)
Turns out that Snow Leopard tries to start Java applications by default with the 64 bit virtual machine which does not work with Simidude because I bundle it with the 32 bit libraries.
Interesting enough when Simidude is launched from the Finder everything works fine…
Now, drum roll please, the solution to this problem is pretty simple:
Open up the Java JRE definition in Eclipse->Settings->Java->Installed JRE edit your standard Java VM and add the following to the “Default VM Arguments”: -d32

Happy Snow Leopard-ing…
I admit, the Simidude user manual was very sparse and lacking much information.
I have worked for the last few days to write up a new user manual that will hopefully be more informative for your and will answer more of your questions.
Special thanks to very helpful user P. Jansen who provided me with a great starting point for this documentation.
The manual is available as PDF from here. I will also include it in future releases of Simidude.
Please let me know any things that I have missed in the manual, also if you’d like to see the documentation in any other format than PDF.
Download the manual here.
Have a great day,
Torsten.
Today I wanted to find the location of a class file to make sure the class is really called from a specific jar file (old project with historically grown piles of archaeologically valuable code).
Turns out this is pretty easy. For instance within the class you log the result of the following statement:
URI uri = this.getClass().getProtectionDomain().getCodeSource().getLocation().toURI()
This will give you the exact place from witch the class was loaded.
A few days ago I release version 1.3.3 of Simidude, the cross platform network clipboard and drag & drop utility.
And now, after I’m sure its working this time I can even write about it
This one is a maintenance release that doesn’t add great new features but it fixes some bugs, renews used libraries and makes it all together more stable. A list of new features and bug fixes is available here.
However I did realize that the update installer for Windows 7 is not working. So when the update checker of Simidude notifies you of an update you can download it but the update installer will then fail (only Windows 7). You can then quit Simidude and start the downloaded installer by hand. I’m sure we’ll figure that one out as well…
Anyway, go grab the latest release from our download site and have fun!
Have a great day,
Torsten.
by tuhlmann on July 16, 2009 Posted in IT
I’m very very sorry for this trouble but today I had to withdraw my Simidude 1.3.2 release again.
There is a major installer problem on the Mac side. I have reports from users that the Windows version works great, so no problem here.
However I added a step to the installer to remove files from previous installations. I told the installer to delete the contents of the installation dir. On Windows this would be “C:\Program Files\Simidude” for instance. On Mac however this is “/Applications” because an application directory is treated as some kind of special file. Alas my installer tried to remove everything from “/Applications” which I only recognized today when I tried to read my mail and my Mail.app program was gone.
Now thanks to Time Machine all the files get rolled back in place, but I sincerely hope no one of you guys was installing 1.3.2 on a Mac!
After properly testing the installer changes on Mac Linux and Windows I’m gonna release a new version- again.
Torsten.
These are the release notes for version 1.3.3 of the cross platform network clipboard Simidude.
I published version 1.3.1 and 1.3.2 earlier this week but had to pull it back due to a problem with the installer.
Version 1.3.3 is a maintenance release that fixed some bugs and brought a few new features:
- Fix: Simidude saves the active clipboard entry to disk so that after a restart of your computer that item can be reloaded and will immediately be available to your system. That mechanism was broken and has now been fixed.
- Fix: Simidude caches files and directories that are transfered between computers into a special cache directory. That directories are removed when the application exits normally. In case of a crash that cache directories remain and will not be removed in the future. That has now been fixed. Cache directories that have no reference to a Simidude item will now be deleted.
- Fix: Simidude crashed when you tried to access it through a browser but where using the server port, not the designated http port. That has been fixed.
- Fix: In some circumstances the written logfile could get huge. Writing of logfile entries has been limited to Error messages and a bug has been fixed that let log files grow endlessly. The Simidude logfile is contained in c:\Users\\.Simidude (Windows Vista and 7). It’s surprisingly called simidude.log.
- Fix: I added an installer option to delete old application libraries from Simidude’s lib dir. That did not workon all platforms.
- Feature: The title bar of the Simidude window now shows the URL you can use with a browser to access it’s entries- if http access is enabled.
This version is recommended for all users.
by tuhlmann on July 9, 2009 Posted in IT
After a day of bug hunting and help from the great guys and gals at Userscape we were able to track down the problem to a wrong ‘include_path’ setting in the PHP preferences.
I have absolutely no clue why this setting was changed during a PHP security update or if it has been there all along. Fact is the problem occured only after the update, and only in this one application. The value of ‘include_path’ was set to ‘.’ in a global confixx file ‘confixx_mhost.conf’. After commenting out the property the whole thing suddenly worked again.
So go ahead and use the helpdesk.
Have a great day,
Torsten.
After a day of bug hunting and help from the great guys and gals at Userscape we were able to track down the problem to a wrong ‘include_path’ setting in the PHP preferences.
I have absolutely no clue why this setting was changed during a PHP security update or if it has been there all along. Fact is the problem occured only after the update, and only in this one application. The value of ‘include_path’ was set to ‘.’ in a global confixx file ‘confixx_mhost.conf’. After commenting out the property the whole thing suddenly worked again.
So go ahead and use the helpdesk.
Have a great day,
Torsten.