Submitted by Tim Towers (not verified) on Sat, 06/19/2010 - 20:15.
Thankyou for writing pocket sudoku.
You have provided me with many hours of entertainment.
I am afraid my old ipaq has become forgotten over the years, and I was wondering if this code could be made to work on a nokia 5800 (which would be a significant challenge) and it occurred to me to try under Ubuntu Linux.
I am pleased to report that after installing the package libmono-winforms2.0-cil the application seems to start up fine apart from a slight hiccup that I think is related to different directory descriptors between Windows and Unix.
An example system call is below:
[0x7f10d6e20740: 1.03818 0] LEAVE: System.Uri:get_LocalPath ()[STRING:0x7f10cda435f0:/home/tim/Sudoku\Languages\English.xml]
where you can see a mixture of / and \ characters in the filename that it is searching for. You can of course get around this issue by linking the file from the subdirectory to one in your home where the '\' characters become part of the filename but it is a bit messy and not obvious. I have read that this issue can be avoided by using something like System.IO.Path.PathSeparator and wondered if when you release version 1.1 you could bear this in mind.
Updated platform support
Thankyou for writing pocket sudoku.
You have provided me with many hours of entertainment.
I am afraid my old ipaq has become forgotten over the years, and I was wondering if this code could be made to work on a nokia 5800 (which would be a significant challenge) and it occurred to me to try under Ubuntu Linux.
I am pleased to report that after installing the package libmono-winforms2.0-cil the application seems to start up fine apart from a slight hiccup that I think is related to different directory descriptors between Windows and Unix.
An example system call is below:
[0x7f10d6e20740: 1.03818 0] LEAVE: System.Uri:get_LocalPath ()[STRING:0x7f10cda435f0:/home/tim/Sudoku\Languages\English.xml]
where you can see a mixture of / and \ characters in the filename that it is searching for. You can of course get around this issue by linking the file from the subdirectory to one in your home where the '\' characters become part of the filename but it is a bit messy and not obvious. I have read that this issue can be avoided by using something like System.IO.Path.PathSeparator and wondered if when you release version 1.1 you could bear this in mind.
Thank you again.