|
I think I saw someone mention it already, but now since I updated if I rotate the app into landscape mode, i can't rotate it back and the app becomes unresponsive and I can't click anything until I close out and reopen the app. It only seems to happen when browsing a forum. It rotates in and out just fine while in a thread or making a reply. This is on an iPhone 6s if it matters.
|
![]() |
|
![]()
|
# ? Jun 10, 2024 14:26 |
|
Iron Prince posted:I think I saw someone mention it already, but now since I updated if I rotate the app into landscape mode, i can't rotate it back and the app becomes unresponsive and I can't click anything until I close out and reopen the app. I don't often use this so I don't know if this has been a thing for a while, but with the latest update this is happening to me too; landscape mode while browsing a forum locks the whole thing up. I'm using a 4S.
|
![]() |
|
Iron Prince posted:I think I saw someone mention it already, but now since I updated if I rotate the app into landscape mode, i can't rotate it back and the app becomes unresponsive and I can't click anything until I close out and reopen the app. I saw it inside threads too, but it's fixed in the latest beta for me.
|
![]() |
|
I get frozen in landscape mode, as well. 5s.
|
![]() |
|
The man called M posted:I get frozen in landscape mode, as well. 5s. Ditto here, 5s too. It was definitely working earlier today before I updated, so it seems to be a new issue.
|
![]() |
|
Portrait Orientation Lock supremacy. ![]() Edit: I get it now. Grundulum fucked around with this message at 08:03 on Jul 2, 2016 |
![]() |
|
Why is the quote icon "6969" now?
|
![]() |
|
Iron Prince posted:I think I saw someone mention it already, but now since I updated if I rotate the app into landscape mode, i can't rotate it back and the app becomes unresponsive and I can't click anything until I close out and reopen the app. I came here to report the same thing but since enough guys already reported it I'll just say thanks for making the app that I use far more than any other app on my phone. Great job!
|
![]() |
|
SKY COQ posted:Why is the quote icon "6969" now? They're rounded quotation marks, like smart quotes or more elaborate fonts. They're getting filled in, I think.
|
![]() |
|
SKY COQ posted:Why is the quote icon "6969" now? Because a conversation is a two way street. Agreed though the single quote mark icon looks a lot better.
|
![]() |
|
Sometimes my bookmark list continually bounce while the loading smiley shows up.
|
![]() |
|
Would it be possible to set the last read post only when I exit the thread, and only to the last post I have seen? I think current behavior matches the website, where last read is set to the end of the current page as soon as you open the thread. The app has the ability to be smarter I would think.
|
![]() |
|
smackfu posted:Would it be possible to set the last read post only when I exit the thread, and only to the last post I have seen? I think current behavior matches the website, where last read is set to the end of the current page as soon as you open the thread. The app has the ability to be smarter I would think. It would require a call to the server for every post you scrolled through, since that's where "last read" is kept. I'm not sure what the semantics would be of having it in two places.
|
![]() |
|
It's clearly 6699 anyway
|
![]() |
|
Omg the pull to next page option. You people are godlike. ![]()
|
![]() |
|
Landscape locks up in v 3.15. Looks like if you open the app and then rotate your phone to landscape mode for either browsing forums or bookmarks that it freezes up. If you're looking in a thread you can go landscape mode, no problem. Clicking the < to go out of a thread back to your bookmarks lets it work without freezing, and you can change to forums, messages, lepers, and settings without it freezing. But if you turn it back to portrait mode, it freezes up then.
|
![]() |
|
Your Dead Gay Son posted:Omg the pull to next page option. You people are godlike. Glad someone else wanted that!
|
![]() |
|
Subjunctive posted:It would require a call to the server for every post you scrolled through, since that's where "last read" is kept. I'm not sure what the semantics would be of having it in two places. I'm thinking last read only needs to be persisted when you leave the thread. So just one extra server call.
|
![]() |
|
smackfu posted:I'm thinking last read only needs to be persisted when you leave the thread. So just one extra server call. I'm not sure how that works with leaving the app and app lifecycle, but that's not an area of expertise for me. I definitely understand the appeal though.
|
![]() |
|
I can imagine fun times trying to define which posts you've seen in threads where image loading makes things jump around.
|
![]() |
|
It feels like the only sensible way to do the last read based on scrolling (what with mobile data/response times) would be to trigger it as/after you leave a page (so it just updates the last read once rather than hitting the server constantly). Only problem with that I guess is should it always trigger that last read no matter what, or is it only pages that you enter 'via' last read, so you're not kicking off last read while browsing an old thread.
|
![]() |
|
I liked when Last Post brought you to the top of the last page better, shoulda just renamed it Last Page instead of "fixing" it ![]() You could always Last Page>Scroll To End but you can't Last Page>Scroll To Top drunken officeparty fucked around with this message at 02:18 on Jul 5, 2016 |
![]() |
|
drunken officeparty posted:I liked when Last Post brought you to the top of the last page better, shoulda just renamed it Last Page instead of "fixing" it Flick the page selector to the bottom and tap Jump. Jump to the last post, then tap the status bar which will scroll to the top of the page. You have options.
|
![]() |
|
carry on then posted:Jump to the last post, then tap the status bar which will scroll to the top of the page. You'd be surprised how few people know about this
|
![]() |
|
carry on then posted:Flick the page selector to the bottom and tap Jump. I have no idea what you are talking about with the first one. I'm sitting here flicking poo poo on my phone to figure it out and feeling dumb. The second one does work though if I can ever remember it when there isn't a big labeled button for it like Scroll To End
|
![]() |
|
People I respected took years to find out about swiping from the edge. Made me sick.
|
![]() |
|
drunken officeparty posted:I have no idea what you are talking about with the first one. I'm sitting here flicking poo poo on my phone to figure it out and feeling dumb. The exact box which has the last post button also has a spinner below it with the page numbers.
|
![]() |
|
carry on then posted:The exact box which has the last post button also has a spinner below it with the page numbers. Oh I see what you mean now. But still, flicking through a 1000 pages of thread to get to the end of the spinner sucks. What am I made of thumbs.
|
![]() |
|
ZeeBoi posted:Sometimes my bookmark list continually bounce while the loading smiley shows up. I don't know what causes this but it's hilarious to watch
|
![]() |
|
The constantly bouncing smiley happens if I've got wifi enabled with proxy but the proxy is down. So likely connection issues aren't resolving quite right.
|
![]() |
|
Please hurry up and figure out what's causing the bug with the bookmark list bouncing continuously while the smiley spins The bug is that it isn't happening for me
|
![]() |
|
Soricidus posted:Please hurry up and figure out what's causing the bug with the bookmark list bouncing continuously while the smiley spins If you have the right music on this is awesome
|
![]() |
|
When I have a thread open in Awful, go to another app and do enough stuff that Awful's evicted from memory, then when I go back to Awful it just loads the beginning of the page. Doesn't even try to jump back to my previous scroll location ![]() Also I haven't seen the bookmark bouncing thing either ![]() ![]() ![]()
|
![]() |
|
Abjad Soup posted:When I have a thread open in Awful, go to another app and do enough stuff that Awful's evicted from memory, then when I go back to Awful it just loads the beginning of the page. Doesn't even try to jump back to my previous scroll location Ditto to both of these I'm sure the app used to be pretty good about scrolling back to where you were if it fell out of memory too
|
![]() |
|
101 posted:Ditto to both of these I always remember it dumping to forums list/bookmarks
|
![]() |
|
if I try copying and pasting a link to a tweet the forums embedded it seems to just be copying https://forums.somethingawful.com
|
![]() |
|
Abjad Soup posted:When I have a thread open in Awful, go to another app and do enough stuff that Awful's evicted from memory, then when I go back to Awful it just loads the beginning of the page. Doesn't even try to jump back to my previous scroll location This remains my most-wanted fix for the next version.
|
![]() |
|
Every thread was telling me I needed archives to view it, so I tried logging out to see if that would fix it... and now I can't log back in. Deleting and reinstalling the app didn't help. I remember reading about a problem like this in this thread before, but I don't remember what the solution was. When I went to log in on a browser to make sure I was typing my password correctly I got an SSL error, though. That could have something to do with it.
|
![]() |
|
Caithness posted:Every thread was telling me I needed archives to view it, so I tried logging out to see if that would fix it... and now I can't log back in. Deleting and reinstalling the app didn't help. I remember reading about a problem like this in this thread before, but I don't remember what the solution was. I'm having the same issue.
|
![]() |
|
![]()
|
# ? Jun 10, 2024 14:26 |
|
zen death robot posted:The forums already work over HTTPS so no big deal Caithness posted:Every thread was telling me I needed archives to view it, so I tried logging out to see if that would fix it... and now I can't log back in. Deleting and reinstalling the app didn't help. I remember reading about a problem like this in this thread before, but I don't remember what the solution was. welp But it seems that QCS already has a mention of this in the tech thread so we'll have to deal with Safari until it's fixed server-side.
|
![]() |