GoogleCodeExporter
commented
8 years ago [deleted comment]Closed GoogleCodeExporter closed 8 years ago
GoogleCodeExporter
commented
8 years ago [deleted comment][deleted comment][deleted comment][deleted comment][deleted comment][deleted comment][deleted comment][deleted comment][deleted comment][deleted comment][deleted comment][deleted comment][deleted comment]File under minor native-UI improvements: In most Mac applications, you can
CMD+click or CTRL+click (right
mouse click) on the title of the window to reveal a simple stack that shows the
finder tree of the open file. It
would be nice if Gargoyle supported this: in other words, by command-clicking
on the title of the game in the
game window, you could see and navigate to the game file's containing folders.Original comment by Ek.Temple@gmail.com on 28 Apr 2010 at 8:26
GoogleCodeExporter
commented
8 years ago [deleted comment]The three diagonal lines in the bottom right corner of a game window,
representing the "pull" for resizing the
window, don't appear in the latest (5/3/2010) build.Original comment by Ek.Temple@gmail.com on 3 May 2010 at 10:07
GoogleCodeExporter
commented
8 years ago [deleted comment][deleted comment][deleted comment][deleted comment]Gargoyle does not "release" game files properly when they are closed. To
replicate:
1) Play a game for a couple of moves.
2) Close the window.
3) In the Finder, delete the game file.
The Finder will respond that the file cannot be deleted, since it is in use by
another program.Original comment by Ek.Temple@gmail.com on 4 Aug 2010 at 1:32
GoogleCodeExporter
commented
8 years ago [deleted comment][deleted comment][deleted comment][deleted comment][deleted comment][deleted comment]Cleaned up some more fixed bugs. The resize widget continues to vex me, but
apart from that we're close to release quality.Original comment by bcressey@gmail.com on 17 Sep 2010 at 12:05
GoogleCodeExporter
commented
8 years ago Using today's build, Gargoyle oesn't seem to notice config files at ~/.garglkrc
or /etc/garglk.iniOriginal comment by vke...@gmail.com on 1 Oct 2010 at 2:25
GoogleCodeExporter
commented
8 years ago Can you post the edited garglk.ini you are using, and let me know what changes
you made? Both locations work for me.
The biggest change in .ini parsing is that propfont / monofont directives
(defined anywhere, including the bundled garglk.ini in the App folder) will
override all existing prop* and mono* directives. So if you are trying to
change fonts the old way, with a hard path to the font file, that won't easily
work now.Original comment by bcressey@gmail.com on 1 Oct 2010 at 3:29
GoogleCodeExporter
commented
8 years ago Oh, it looks like /etc/garglk.ini will generally get overridden by the bundled
ini file. So that's probably not a very useful place to put the custom config.Original comment by bcressey@gmail.com on 1 Oct 2010 at 3:51
GoogleCodeExporter
commented
8 years ago Well, this is rather embarrassing, but since I have a habit of double checking
things. I was going to try and reproduce the issue before I replied. ...It
works now, I'm just going to chalk this up to user error. Sorry for wasting
your time and thanks for the quick help anyways.Original comment by vke...@gmail.com on 1 Oct 2010 at 7:24
GoogleCodeExporter
commented
8 years ago No problem, glad to hear it's working!
Added a crash report I ran into this morning. Haven't been able to repro it
yet; if anyone sees something similar please post it from ~/Library/Logs.Original comment by bcressey@gmail.com on 1 Oct 2010 at 3:12
Attachments:
GoogleCodeExporter
commented
8 years ago Given the overall stability of the Mac port, I'm marking this as closed.
Individual bugs can be opened as new issues are discovered.Original comment by bcressey@gmail.com on 16 Mar 2011 at 6:32
Original issue reported on code.google.com by
bcressey@gmail.comon 7 Mar 2010 at 5:57