Closed GoogleCodeExporter closed 9 years ago
Eric,
Have you tried setting Witty's proxy configuration in the options menu? Click
on the
"Options" button, then the "Connection" button to see Witty's proxy settings.
Brian
Original comment by bmsulli...@gmail.com
on 9 Apr 2008 at 4:50
Brian,
I cannot get past the username/password dialog box. The "Options" button, or
any of
the other buttons (except "Login"), is grayed out. If I press Esc to ignore the
login request, Witty exits completely.
Eric
Original comment by eric.t...@gmail.com
on 9 Apr 2008 at 5:28
Alan,
Should we enable the Options button before logon? I thought I had tested this
when I
was making the proxy enhancements, but it looks like it works a bit differently
now.
Brian
Original comment by bmsulli...@gmail.com
on 9 Apr 2008 at 5:40
Yes. with connection and proxy options now, the interaction should allow for
users to
set that up before connecting. We do need to make sure that there aren't new
bugs
introduced by enabling the options menu.
Original comment by alan...@gmail.com
on 9 Apr 2008 at 7:16
As it stands now, I couldn't get a fresh install of Witty 0.1.8b1 to work
without
manually editing my proxy info to the config file. (App would start and try to
log
in, which is impossible until it knows my proxy settings, which Witty won't
allow me
to enter until I'm logged in. :))
Why not just have Witty check the system-wide proxy settings as the OP
suggested?
Regardless, Witty is terribly useful. Thanks for all your hard work on it.
Original comment by kmarn...@gmail.com
on 21 May 2008 at 8:39
see patch attached to comment #1 on issue #104
Original comment by grn...@gmail.com
on 29 May 2008 at 5:32
As of revision 346: Option button is always enabled now to allow for editing
proxy
settings before login attempt occurs. Also made modification to improve the
proxy
support (similar in nature to grnfvr's patch, but I had already done separely
in my
own branch which was merged with the official source).
Original comment by jfol...@gmail.com
on 16 Jul 2008 at 6:15
Original issue reported on code.google.com by
eric.t...@gmail.com
on 8 Apr 2008 at 7:56Attachments: