One thing noticed during elimination, and it's only since new icons been implemented is that when select from "Items" the 'take' selection is now off the display to the left on mobile phone. Is there some display setting I need to adjust with the mobile display to correct this, as currently need use script to select and item to quick access so that I can use the item I.e. drugs, alcohol, cans etc.
Mobile display
Started by Noodles [1860503] on in Bugs & Issues.
About this thread
Posts archived: 6 / 6 posts (100%) · the total is Torn's reply count + the opening post at the last fetch
Counted by TornLife from the archived posts.
- Archived posts
- 6
- Discussion span
- →
- People posting
- 3
- Likes on archived posts
- 1
- Posts by staff, officers and moderators
- 3
- Authority score
- 55 / 100
- Historical score
- 27 / 100
- Story score
- 33 / 100
- Engagement score
- 42 / 100
The option to Use/Take has always been on the left side and it should be perfectly accessible without requiring scripts. Can you provide a screenshot of what you are seeing?
[image: i.imgur.com]
[image: i.imgur.com]
![[image: i.imgur.com]](https://i.imgur.com/Og9wtrt.png){kind=link}
https://imgur.io/a/tODGQLE
Hopefully can view the hyperlink. Tried post image but get error msg (me having brain fart error I expect trying post link)
Hopefully can view the hyperlink. Tried post image but get error msg (me having brain fart error I expect trying post link)
That's not a native Torn option, you are using an extension/script that is adding an extra button to the row, Torn cannot fix that.
[image: i.imgur.com]
Thanks!
[image: i.imgur.com]
![[image: i.imgur.com]](https://i.imgur.com/7ZHkWV6.png){kind=link}
Thanks!
But even script to +add could still see and use take button; worked fine for years, only recent week's cannot. Hence query about display setting for mobile if need to adjust as only occurred since image updates. Guess need get with Hensley, adjust display 85%
The + add button is part of ReTorn. It is a display bug on very small screens. It has been fixed and will be updated as soon as Chrome accepts the latest update.