@anapospastos @planetf1, right now I think the most important things are addition of a few more core twitter functions, such as DM, and follow/unfollow. I'm ok with not having image upload via the client right now coz the upload function from the gallery is quite decent.
I actually want to see lists feature at least somewhere,because witter doesn't have it either.
I just tried chir.ps and audio tweets! Its not working from microb browser so an idea landed to me! If you can implement audio tweets to tweego will be awesome)
Hi,
the same timestamp issues here.
Tweet time is always 0:0 1 jan 1st.
My timezone is GMT+2
Timeformat 24hour.
Another issue:
Can the auto-capitalization for the username
entry box be turned off?.
And turn of the dictionary support for the password field?
(I don't like to see my passwords as text suggestion in other
textfields).
Other notes:
The logoff confirmation dialog asks "Are you sure you want to quit?"
The same text is used by the "exit" confirmation dialog.
Btw I would prefer to not ask the user for confirmation after he
pressed the exit button.
Hi,
the same timestamp issues here.
Tweet time is always 0:0 1 jan 1st.
My timezone is GMT+2
Timeformat 24hour.
You should use
QLocale::setDefault(QLocale::English);
and
QDateTime tweetDate = QLocale().toDateTime(createdAt,"ddd MMM dd HH:mm:ss yyyy");
to parse the timestring.
Twitter uses english time format
and QDateTime::fromString() uses the default system
timeformat (device locale).
I've just noticed that it appears to be posting a tweet twice. Don't know if anyone else has notiiced this. It doesn't show it on the timeline, but if you go into the profile on the internet it will be there twice.
You should use
QLocale::setDefault(QLocale::English);
and
QDateTime tweetDate = QLocale().toDateTime(createdAt,"ddd MMM dd HH:mm:ss yyyy");
to parse the timestring.
Twitter uses english time format
and QDateTime::fromString() uses the default system
timeformat (device locale).
regards
Nicolai
how do you use this, I see no prefs or settings in tweetgo
)