Skip to content

[android] chat dialog cannot be closed #1763

Closed

Description

@henkdegroot

Describe the bug
When the chat window opens on Android, it uses the fullscreen and does not allow to return (close) the window to get back to the main dialog.

To Reproduce
Open the app on Android and open the Chat window
When using a server that has "license" enabled, you automatically get the chat window displayed and cannot even the app at all.

Expected behavior
A close option should be available to the Chat window on Android device (perhaps on iOS as well).
The default x (available in other platforms) does not show on Android.

Operating system
Android 10

Version of Jamulus
3.8.0rc1

Activity

  1. ann0see commented on May 26, 2021

    @ann0see
    Member

    I think #1512 will fix this

  2. linked a pull request that will close this issueiOS sound support #1512on May 26, 2021
  3. henkdegroot commented on May 26, 2021

    @henkdegroot
    ContributorAuthor

    Wow...that is a very quick solution! Works correct indeed....I had seen the PR a while ago...and thought it was merged already.
    Guess I was mistaken and should have checked first.

  4. dcorson-ticino-com commented on May 26, 2021

    @dcorson-ticino-com
    Contributor

    I think the solution is a one window interface, if we decide to use it.
    Here is a first stab at something useful:
    #1343 (comment)

  5. ngocdh commented on May 26, 2021

    @ngocdh
    Contributor

    one window interface

    @dcorson-ticino-com I love it actually. But I have to disagree here, because of mobile devices' small screens.
    For desktop, I vote for one window interface.

  6. ann0see commented on May 26, 2021

    @ann0see
    Member

    Yep. That's what Jamulus might look like in future ;-). However I suggested small steps to not confuse users.

  7. henkdegroot commented on May 26, 2021

    @henkdegroot
    ContributorAuthor

    mobile-preview

    It is not that bad at all on my mobile (screen resolution of 720 x 1480).....a few tweaks here and there...and we are back into the future :)

  8. dcorson-ticino-com commented on May 26, 2021

    @dcorson-ticino-com
    Contributor

    But I have to disagree here, because of mobile devices' small screens.

    Then I am totally confused. If the screen is too small, use a device with a screen size that is OK.
    Why do you want to use it at all?
    I can't imagine how this should work if every time a chat comes the screen changes, one would spend more time playing with ones device than playing ones instrument.
    The other guy who posted today about his Android had a screen resolution that is higher than on my PC. With that even the normal Jamulus interface should work just as well as on a PC.
    Apparently these devices don't let you use that resolution. :(

  9. ngocdh commented on May 26, 2021

    @ngocdh
    Contributor

    It is not that bad at all on my mobile (screen resolution of 720 x 1480).....a few tweaks here and there...and we are back into the future :)

    I'd love for those tweaks to happen. Because as it is now, if you're in a room with 10, you'll have to deal with small scrollbars which are hard to use (touch screen gestures not supported now). And those settings tabs, also hard to click on.

    So if there's a way for everything to fit nicely and not so hard to manœuvre, I'm in.

  10. ngocdh commented on May 26, 2021

    @ngocdh
    Contributor

    Why do you want to use it at all?

    Because it's practical.

    one would spend more time playing with ones device than playing ones instrument.

    Which is why mobile apps must have their own design so that it's easy for users to use. Take chat window example: for mobile devices we could use notifications instead of the whole window.

    Some mobile devices might have high resolution, but that also means controls are small on a (relatively) small screen, which makes them hard to use. At least that's what I get from using current Jamulus on mobile devices.

    But I'm sure we can make it better :)

  11. added a commit that references this issue on Jun 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions