Game Development Community

iT2D 1.4 - Use of custom OSX folder icons - RESOLVED

by Craig Fortune · in iTorque 2D · 08/17/2010 (12:43 pm) · 6 replies

1.4 Release

Platform:
OSX

Where:
Problem happening with SVN (unsure of git as I don't use it)

Issues:
The use of a custom folder icon for the "iTorque2D_1_4" directory of a normal installation is actually pretty unhelpful! The way these icons files are stored (within the folder, but hidden by a standard OSX setup) will cause issues with SVN commits. This is due to specific file naming convention used conflicts with other operating systems, and most notably with SVN clients.

Even trying to "ignore" this file in SVN can cause issues.

Steps to Repeat:
1. Try an SVN commit of the root folder of an iT2D project

Suggested long term fix:
Simply don't use these icons in future releases.

Suggested short term DIY fix:
Use a tool called "A Better Finder Attributes" to enable the showing of hidden files within OSX. Nuke the icon file.

#1
08/17/2010 (5:29 pm)
Ouch. That's definitely not a good thing. I'll look into this immediately. We are looking at a 1.4.1 beta sometime soon, so this may be added to the list since it's a simple fix and manual step that can be avoided.
#2
08/17/2010 (5:51 pm)
Yea it is easy as pie to fix, would be daft not to include this in the next beta imo.
#3
08/17/2010 (7:04 pm)
The problem is Subversion, honestly. And you shouldn't be checking the entire installation in anyway :)

I find posts going years back about SVN not handling many special characters in filenames, and it still hasn't been fixed in any reasonable way. Some have patched their versions to accept them without trouble, though.
#4
08/18/2010 (12:15 pm)
I never said the problem wasn't SVN... I'm just saying that it isn't a good idea to use custom icons because SVN misbehaves with them :)

As for checking in a whole installation, well that is pure opinion/preference thing not a "should/shouldn't" thing imo.
#5
08/24/2010 (8:43 pm)
Logged as an improvement in Jira, ITGB-83. Marked for 1.4.1 release.
#6
03/09/2011 (10:17 am)
Fixed in 1.4.1.