Forum Replies Created

Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • in reply to: requirements: more touchpad (relative touch) function #24913
    qstdnx
    Participant

    Why do I request this feature?
    Many software in windows are designed for mouse clicks. When I use touchscreen method, there will be some bug. so I have been using relative touch. I think this is similar to using the touchpad of a laptop to control the mouse which can handle all situations, and it should support the gestures of the windows touchpad.

    in reply to: requirements: more touchpad (relative touch) function #24911
    qstdnx
    Participant

    Hi @christian
    Thank you for your reply.
    Because absolute touch can’t handle all situations with me, I usually use relative touch all the time. But relative touch triggers menus and scrolls is too inefficient. I hope to give priority to support these two gestures at least, including Two finger click trigger menu, Two finger slide trigger scrolling.

    • This reply was modified 9 months, 3 weeks ago by qstdnx.
    in reply to: Remote Audio bug #17950
    qstdnx
    Participant

    @qstdnx
    Well, if you can’t reproduce it, maybe the problem lies in my screen or system.

    in reply to: Remote Audio bug #17936
    qstdnx
    Participant

    @spacedesk Lea
    Thank you again for your reply.
    According to your method, my computer still cannot re-recognize the S1 speaker. I still can only recover by rebooting.
    As long as my computer is not connected to S2, even if I disconnect S1, the computer will be able to recognize S1 speakers after reconnecting. I used my phone to install spacedesk for testing, and the same situation occurred. As long as I didn’t use the spacedesk screen, unplugged or disconnected S1 will without causing the problem of not recognizing the speakers.
    By the way, did you reproduce the same bug?

    • This reply was modified 1 year, 3 months ago by qstdnx.
    in reply to: Remote Audio bug #17898
    qstdnx
    Participant

    @spacedesk Lea
    I’m very sorry that I didn’t test it clearly when I gave you feedback, so you can’t reproduce it.
    After testing, I found that everything was fine when I used both the HDMI screen (hereinafter called S1) and the Android tablet installed spacedesk (hereinafter called S2). The operation of bug reproduction is as follows:
    After the S2 is connected to the computer, in multi-monitor setting(Windows Settings→System→screen), set S1 to disconnect, and only use S2 as the screen. In this case, if the spacedesk is disconnected, S1’s speakers will not be recognized. This is how I usually use spacedesk, so I’ve been obsessed with this bug.
    the same bug occurs when the HDMI cable is unplugged and then connected.
    Please find attached a copy of the file you requested in following link.
    https://pan.huang1111.cn/s/jl9oUy
    Because the file exceeds the forum file size limit:(
    Thank you again for your reply. Please let me know if you need more information.

    in reply to: Remote Audio bug #17897
    qstdnx
    Participant

    @spacedesk Lea
    I’m very sorry that I didn’t test it clearly when I gave you feedback, so you can’t reproduce it.
    After testing, I found that everything was fine when I used both the HDMI screen (hereinafter called S1) and the Android tablet installed spacedesk (hereinafter called S2). The operation of bug reproduction is as follows:
    After the S2 is connected to the computer, in multi-monitor setting(Windows Settings→System→screen), set S1 to disconnect, and only use S2 as the screen. In this case, if the spacedesk is disconnected, S1’s speakers will not be recognized. This is how I usually use spacedesk, so I’ve been obsessed with this bug.
    the same bug occurs when the HDMI cable is unplugged and then connected.

    in reply to: Remote Audio bug #17896
    qstdnx
    Participant

    @spacedesk Lea
    I’m very sorry that I didn’t test it clearly when I gave you feedback, so you can’t reproduce it.
    After testing, I found that everything was fine when I used both the HDMI screen (hereinafter called S1) and the Android tablet installed spacedesk (hereinafter called S2). The operation of bug reproduction is as follows:
    After the S2 is connected to the computer, in multi-monitor setting(Windows Settings→System→screen), set S1 to disconnect, and only use S2 as the screen. In this case, if the spacedesk is disconnected, S1’s speakers will not be recognized. This is how I usually use spacedesk, so I’ve been obsessed with this bug.
    the same bug occurs when the HDMI cable is unplugged and then connected.
    Please find attached a copy of the file you requested in following link.Because the file exceeds the forum file size limit:(
    https://pan.huang1111.cn/s/jl9oUy

    Thank you again for your reply. Please let me know if you need more information.

    in reply to: Remote Audio bug #17894
    qstdnx
    Participant

    @spacedesk Lea
    I’m very sorry that I didn’t test it clearly when I gave you feedback, so you can’t reproduce it.
    After testing, I found that everything was fine when I used both the HDMI screen (hereinafter called S1) and the Android tablet installed spacedesk (hereinafter called S2). The operation of bug reproduction is as follows:
    After the S2 is connected to the computer, in multi-monitor setting(Windows Settings→System→screen), set S1 to disconnect, and only use S2 as the screen. In this case, if the spacedesk is disconnected, S1’s speakers will not be recognized. This is how I usually use spacedesk, so I’ve been obsessed with this bug.
    the same bug occurs when the HDMI cable is unplugged and then connected.
    Please find attached a copy of the file you requested in following link.
    https://pan.huang1111.cn/s/jl9oUy
    Because the file exceeds the forum file size limit:(
    Thank you again for your reply. Please let me know if you need more information.

    in reply to: Remote Audio bug #17905
    qstdnx
    Participant

    I don’t know why I can’t send out what’s said in the picture.(눈 눈)

    in reply to: Remote Audio bug #17903
    qstdnx
    Participant

    https://pan.huang1111.cn/s/jl9oUy

    Attachments:
    You must be logged in to view attached files.
    in reply to: Remote Audio bug #17899
    qstdnx
    Participant

    I’m very sorry that I didn’t test it clearly when I gave you feedback, so you can’t reproduce it.

    • This reply was modified 1 year, 3 months ago by qstdnx.
    • This reply was modified 1 year, 3 months ago by qstdnx.
    • This reply was modified 1 year, 3 months ago by qstdnx.
    in reply to: Remote Audio bug #17895
    qstdnx
    Participant

    Why I can’t see my reply.

    in reply to: Remote Audio bug #17814
    qstdnx
    Participant

    @spacedesk Lea
    Thank you for your patient reply.
    When the speaker of the screen with the HDMI interface is not recognized, the speaker of the screen is not displayed in the Sound setting. I’ve tried to switch the spacedesk OFF-ON too, and it won’t make the device to be re-recognized.
    There was the same problem in the previous version, and I found a solution. Before I disconnect, I let the computer sleep, and then disconnect the computer after sleep, so that the device will be recognized when I wake up the computer. If the spacedesk is disconnected while the computer going to sleep, the speakers on the screen will still not be recognized after waking up the computer.
    But in the new version of spacedesk, this method has failed. The last version of spacedesk I installed was 0.9.76
    I hope it will help you solve this bug. Please let me know if you need more information.

    • This reply was modified 1 year, 3 months ago by qstdnx.
Viewing 13 posts - 1 through 13 (of 13 total)