Re: Issue 100 in ntorrent: Profile Will Not Save In Mac Version

1 view
Skip to first unread message

codesite...@google.com

unread,
Dec 5, 2009, 5:17:34 PM12/5/09
to ntorr...@googlegroups.com

Comment #20 on issue 100 by roy.verrips: Profile Will Not Save In Mac
Version
http://code.google.com/p/ntorrent/issues/detail?id=100

This is still a problem with nTorrent-0.5.1 on Mac (Tested with Mac OSX
10.6.2) - The
workaround in Comment 19 (1st April 09) still works though.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

codesite...@google.com

unread,
Dec 6, 2009, 6:08:40 AM12/6/09
to ntorr...@googlegroups.com
Updates:
Status: Accepted

Comment #21 on issue 100 by kei060: Profile Will Not Save In Mac Version
http://code.google.com/p/ntorrent/issues/detail?id=100

yes thats right, but i think (emphasis on "think") it may have been fixed
in trunk.
So i guess you just have to wait to the 0.6 version. not a minor release as
0.5.1 ;)

codesite...@google.com

unread,
May 9, 2010, 6:19:16 PM5/9/10
to ntorr...@googlegroups.com

Comment #22 on issue 100 by neutrina.einzig: Profile Will Not Save In Mac
Version
http://code.google.com/p/ntorrent/issues/detail?id=100

I have the same issue on Leopard. Comment 19 helped me. Thanks,
b.g.l.nelissen! But I
think that this issue is a bug.

--
You received this message because you are subscribed to the Google Groups "ntorrent.dev" group.
To post to this group, send email to ntorr...@googlegroups.com.
To unsubscribe from this group, send email to ntorrentdev...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/ntorrentdev?hl=en.

codesite...@google.com

unread,
Apr 13, 2011, 9:51:24 PM4/13/11
to ntorr...@googlegroups.com

Comment #23 on issue 100 by kenxl...@gmail.com: Profile Will Not Save In
Mac Version
http://code.google.com/p/ntorrent/issues/detail?id=100

ntorrent 0.5.1 still have this problem on 10.6.7.
But the workaround in comment 19 does work.

Reply all
Reply to author
Forward
0 new messages