mscarrot | # 271 | 2010-03-23, 16:04 | Report

It doesn't register anything..
it says from running standalone: (and tried to (twice) send a tweet)

getting tweets with PaulaN900
base url = https://twitter.com/
base url of api object = https://twitter.com/statuses/friends_timeline.json
running tasks 0
fetched image
updating all stored images for 41692369

So it seems like it isn't noticing my tweet at all right??

---

Last edited by mscarrot; 2010-03-23 at 16:05. Reason: add more tekst

dwould | # 272 | 2010-03-23, 16:09 | Report

so is that what output after you hit the W button to tweet? or was that already output and nothing additional output when you hit the W button?

mscarrot | # 273 | 2010-03-23, 16:17 | Report

that was already the output and no additional output after I've hit the W button (tried several times)

dwould | # 274 | 2010-03-23, 16:51 | Report

I'm totally flummoxed, There should be no way to press the button and get no response at all, either you would get a banner saying success or one saying failure.
As it turns out there isn't any diagnostic output on that path that would go to the terminal (though I just added some to the source for future needs)

I can't even guess at what is wrong, since it should be impossible to get no feedback at all from pressing the button.
I'll keep thinking

mscarrot | # 275 | 2010-03-23, 17:07 | Report

Thanks, but I also don't get a banner at all,
it only shows the moving circle (next to the for a while but that changes to nothing soon, don't get a failure banner after that...

But am wondering if I am the only one with this problem hmmm strange...

Update: even after configure Oauth again problem still exists

dwould | # 276 | 2010-03-23, 17:19 | Report

how comfortable are you with a little hacking...?
if you want to try to get more informaiton go to xterm
sudo gainroot (or however you prefer to get root access)
vi /opt/witter/witter.py
scroll down to line 219 which should be the 'enterPressed' method

go into insert mode (i)
and add some print lines either side of the call to newTweet, like so:
print "sending tweet"

result = self.activeAccount.newTweet(self.ui.getEntryText() , reply_to_name=self.reply_to_name, reply_to_id=self.reply_to)

print "Tweet Sent"

then press ESC, and then :wq
to save and exit vi
Then re-run witter. This should at least show if the event notification is triggering the method at all.
also in that method immediately after that there is an if (result=True)
statement, if you put in there
print "tweet successful"
and in the else block
print "tweet failed"
then if for some reason the banner stuff isn't working, then the output should at least show whether witter things it's succeeding in posting or not.

If you don't fancy doing that, then you may have to wait until I get around to a 0.3.1-6 at which point I have put those changes in the code.

mscarrot | # 277 | 2010-03-23, 17:26 | Report

Daniel,

Will look into that later, am not sure I'm into the hacking stuff but if you described it correctly I can't go wrong right??

Of course would like to provide you more info about this problem,
you are giving us a great (and free) program so it is only a little effort to help you in return !!

dwould | # 278 | 2010-03-23, 18:33 | Report

nevermind...just uploaded 0.3.1-6 to fix twitpic and it contains those new log statements.
give it a whirl and see what it says

nosa101 | # 279 | 2010-03-23, 18:54 | Report

Witter is looking good. Sent you a follow request on Twitter. Glad to help with the testing
there is no auto refresh, right?

dwould | # 280 | 2010-03-23, 19:01 | Report

look under preferences...