d4n93rm0u53 Posts: 4 06/05/2009	d4n93rm0u53 Posts: 4 First of all let me say that this project has been very well designed and implemented. I do however one suggestion: The way in which application paths are stored currently seems to be via an absolute path, minus the drive letter which is presumably provided during runtime. My current setup involves multiple workstations and I like where possible to mirror my setup across all systems, I achieve this via a number of synchronisation scripts. Because my systems are made up of a mixture of x64 and x86 hardware (along with differing OS versions), I have found that when I mirror your application the paths stored within are left corrupted. My suggestion then is that you might offer the option of a relative path, and addition to the current fix path solution. I'm not sure if this is a feasible option, but if possible I believe it will make the project more versatile.
	link
Gianluca Administrator Posts: 1274 07/05/2009	Gianluca Administrator Posts: 1274 Thank Chris for you suggestion. Relative paths will be implemented from version 1.05 for all SyItem residing below SyMenu root folder.
	link
Gianluca Administrator Posts: 1274 22/06/2009	Gianluca Administrator Posts: 1274 SyMenu 1.05 has been released. From this version paths residing on the same SyMenu drive will be relative. Universal Unit Identifier (#:/) remains for compatibility reasons and to store dynamic paths on command parameters, but SyMenu works out relative paths for new items. SyMenu won't convert old Universal Unit Identifier paths in relative paths automatically. If you prefer this new path type, you can re-import any programs (with batch importer) or refresh any path one by one with browse button. Bye Gianluca <em>edited by Gianluca on 16/07/2009</em>
	link

---