Conversation:
Notices
-
@alexivanov Yes, thank you. We noticed this already https://github.com/andstatus/andstatus/issues/362
Action bar is placed too deep in the screen layout, so it can be covered by the Editor.
Current workaround is to turn your device in landscape orientation and then press Send button, which appears to the right. https://loadaverage.org/attachment/3016245
-
@alexivanov Actually it's not bad that you can use Action bar space on a small device.
I need to think how to preserve this unexpected gain and still allow to edit long posts/replies to long posts on small devices...
@moshpirit
-
@moshpirit I didn't get what you mean, please explain.
-
@moshpirit Yes, since v.25 single tap is used for a Context menu, please read the Change log.
You can return to old behavior via Settings -> Gestures -> "Long Tap to open Context menu"
-
@alexivanov @moshpirit Expanding the Editor area down from an Action bar? Why this idea didn't come to me? :-) ... Anyway, current problem is not caused by direction of the Editor growth. It is caused by too large maximum height of this growth. I will try to do this: 1. Return Action Bar to the same place it was before (i.e. not covered by Editor) 2. Allow to switch to a full …
-
@alexivanov I fixed Action bar absence and implemented Editor expanding from the Action bar down. Works but looks unusual...
Will play with alternative placements, add editor collapsing and publish next release...
@bulletbites @mra757 @moshpirit
-
@alexivanov @moshpirit I published v.26.01 to the Beta channel https://play.google.com/apps/testing/org.andstatus.app
Message Editor improvements:
* Fixed: Editor window covered Action Bar if replying to a long message. #362
* Text box with a text of the new message is scrollable vertically now.
* Fullscreen mode toggle by tapping on not editable parts of the Editor.
@nepfag @bulletbites @mra757
-
@bulletbites In addition to what you already mentioned regarding help to the AndStatus project I want to add this: 1. Participation in Beta testing with feedback on bugs found and fixed via the Issues list at http://status.hackerposse.com/url/7514 (and sending Crash reports by email). Opt in for the Beta testing here: http://status.hackerposse.com/url/8179 As number of active u…
-
@alexivanov I noticed this also. But this is a minor problem compared to how it was before...
-
@alexivanov In practice, it is often hard and time consuming to find out a cause of a problem, when someone reports a bug in a post. Because context of investigation and fixing is being lost very quickly. Except for trivial cases. History of discussions is often lost, and it's not easy to find similar case. Two - way communication in a specialized place is far more effective. …
AndStatus
All Hacker Poesy content and data are available under the 