Entries for January 2009

I had a user alert me of a UI issue that was preventing him from using the new global configuration file feature. I uploaded version 1.0.2 to take care of this issue.

Here is a list of changes:

NEW

• Install script now has update logic. Don't need to uninstall previous version.

FIX

• UI logic was preventing the usage of the global configuration file functionality.
• Install script will now correctly install into the C:\Program Files\x86 directory in 64bit systems.

Please go to the PainlessSVN Downloads page to get it.

I just uploaded the lastest release of Text File Splitter. Here is the new stuff: 

NEW

• Added the ability to specify file patters naming conventions.
• Added the ability to omit boundary lines from the chunk files when using regular expressions and text boundaries.
• Added the ability to use the boundary lines as chunk file names. This only works when used with regular expression boundary check.

CHANGED

• Added a tabbed control to better organize the split by choices.

Please go to the downloads page to get this new version.

I am happy to announce that PainlessSVN 1.0.1 is now ready for general consumption. Here is a list of what is in this update:

NEW

• Payment is now done by FastSpring
• Global configuration file support
• The new information panel for the Subversion server
• Realms - View Only

FIX

• Bugfixes for a few UI issues
• Fixed licensing to support new scheme

Please uninstall version 1.0.0 before installing this update.

I have reset the 30 day trial, so everybody that had 1.0.0 can test this for another 30 days.

I'm holding a sale until January 31, 2009. PainlessSVN will be 50% off until then. That means that you can get buy it for $24.97. International customers should now be able to use their own currency.

There's a small issue on Vista 64, where the installation will not use the C:\Program Files (x86)\SystemWidgets folder. It will install on C:\Program Files. I tested this on Windows Vista Ultimate 64, and on Windows 2008 Server 64 and it is working fine. Apparently, Vista is doing some dodgy stuff. This is non-standard behavior, and Microsoft is aware of it.