Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Long(V3) Onion address is not wrapped in peer details #262

Open
ghost opened this issue Mar 29, 2021 · 9 comments
Open

Long(V3) Onion address is not wrapped in peer details #262

ghost opened this issue Mar 29, 2021 · 9 comments
Labels
UI All about "look and feel" UX All about "how to get things done"

Comments

@ghost
Copy link

ghost commented Mar 29, 2021

In the upper right corner of the screenshot you can see that the long(V3) Onion address is not wrapped, but cut.
Also, the colon before the port is missing, which is confusing.

When you enlarge the detail window, you can see that wrapping automatically works, but only at word-breakpoints, e.g. space or colon.

kein_doppelpunkt

Copying the v3 Onion address and port with the mouse works fine, though. The complete address and port is copied.

@hebasto hebasto added the Bug Something isn't working label Mar 29, 2021
@hebasto
Copy link
Member

hebasto commented Mar 29, 2021

Will a contraction of presented address like fbuf3g…a27cad.onion:8333 work for you?

@ghost
Copy link
Author

ghost commented Mar 29, 2021

I would like it better, if the address would be longer than 28 31 characters (which is half of the onion V3 length 56 + : + 5 digit port number) it would get a linefeed wrap after the 28 31th character. I think this would fit well into the window, and there would be no information loss.

But the whole address should be copy-able.

I did not find another way to copy the address, aside of marking it in the details tab with the mouse (this was also the use case made me stumbling upon this issue).

Alternatively, if right-cklicking the address in the main peer window column, there could be a context menu "copy to clipboard". I would like that most.

@hebasto
Copy link
Member

hebasto commented Mar 30, 2021

@wodry

Do you mind looking into #264?

@ghost
Copy link
Author

ghost commented Mar 30, 2021

Do you mind looking into #264?

Have done, thank you very much. If this copy-menu is there, the detail window regarding the node address is not so important anymore, and I could live with a contracted address display like fbuf3g…a27cad.onion:8333 there.

@hebasto hebasto added Design and removed Bug Something isn't working labels Apr 10, 2021
@hebasto
Copy link
Member

hebasto commented Apr 10, 2021

@wodry

... contracted address display like fbuf3g…a27cad.onion:8333 there.

Done in #276.

hebasto added a commit that referenced this issue Apr 19, 2021
4e06133 qt: Elide long strings in their middle in the Peers tab (Hennadii Stepanov)

Pull request description:

  The eliding of long addresses (Onion v3 etc) in the Peers tab in their middle was [discussed](#262 (comment)) in #262.

  On master (f0fa324):
  ![DeepinScreenshot_select-area_20210410141435](https://user-images.githubusercontent.com/32963518/114267903-24eea400-9a07-11eb-8c80-99f68d5cc522.png)

  With this PR:
  ![DeepinScreenshot_select-area_20210410140430](https://user-images.githubusercontent.com/32963518/114267796-83675280-9a06-11eb-921f-ca47c2075496.png)

  This PR suggests the minimal diff to achieve the goal. OTOH, this change in behavior is common for all columns in the Peers table, but it seems harmless.

ACKs for top commit:
  jarolrod:
    tACK 4e06133
  promag:
    Code review ACK 4e06133.

Tree-SHA512: 1d5a62afb1152029e69fccea2ae53dcb262a91724a5c03dfc4de8c409b280814d0c211c2f9a71f1a6e927f4ed571ba4ac311de9de8ebb797eaf1051674241bdb
sidhujag pushed a commit to syscoin/syscoin that referenced this issue Apr 19, 2021
… Peers tab

4e06133 qt: Elide long strings in their middle in the Peers tab (Hennadii Stepanov)

Pull request description:

  The eliding of long addresses (Onion v3 etc) in the Peers tab in their middle was [discussed](bitcoin-core/gui#262 (comment)) in #262.

  On master (f0fa324):
  ![DeepinScreenshot_select-area_20210410141435](https://user-images.githubusercontent.com/32963518/114267903-24eea400-9a07-11eb-8c80-99f68d5cc522.png)

  With this PR:
  ![DeepinScreenshot_select-area_20210410140430](https://user-images.githubusercontent.com/32963518/114267796-83675280-9a06-11eb-921f-ca47c2075496.png)

  This PR suggests the minimal diff to achieve the goal. OTOH, this change in behavior is common for all columns in the Peers table, but it seems harmless.

ACKs for top commit:
  jarolrod:
    tACK 4e06133
  promag:
    Code review ACK 4e06133.

Tree-SHA512: 1d5a62afb1152029e69fccea2ae53dcb262a91724a5c03dfc4de8c409b280814d0c211c2f9a71f1a6e927f4ed571ba4ac311de9de8ebb797eaf1051674241bdb
@hebasto hebasto added UI All about "look and feel" UX All about "how to get things done" and removed Design labels May 8, 2021
@jarolrod
Copy link
Member

jarolrod commented Jul 6, 2021

@wodry can this can be closed since #276 was merged?

I could live with a contracted address display like fbuf3g…a27cad.onion:8333 there.

@ghost
Copy link
Author

ghost commented Jul 6, 2021

The use case I stumbled upon this issue was that I wanted to copy a peer address, and it was confusing to try to copy it from the details header where it was not wrapped.

#276 (shorten address display with '...' in the middle) is not regarding this issue.

This issue would be solved with a copy entry in the addresses context menu. That was intended with #264, which was closed and then picked up in #318, which is still open, not merged. The "copy address" address context menu entry is missing in current master:
screenshot
From my point of view, this could be closed when #318 would be merged.

@ghost
Copy link
Author

ghost commented Jul 6, 2021

@wodry can this can be closed since #276 was merged?

I could live with a contracted address display like fbuf3g…a27cad.onion:8333 there.

You dropped the first part of my sentence:

"If this copy-menu is there, [...] I could live with a contracted address display like fbuf3g…a27cad.onion:8333 there."

@hebasto
Copy link
Member

hebasto commented Jul 27, 2021

"If this copy-menu is there, [...] I could live with a contracted address display like fbuf3g…a27cad.onion:8333 there."

The Qt widget which is used to represent peer addresses (i.e., peerWidget which is an instance of QTableView) by default supports copying from a cell to a clipboard with keyboard shortcuts -- Ctrl+C on Linux/Windows, or ⌘+C on macOS.

So, the requested functionality is available in the code base. The new "Copy Address" context menu item just adds another way to perform the same action.

PastaPastaPasta pushed a commit to PastaPastaPasta/dash that referenced this issue Oct 20, 2021
… Peers tab

4e06133 qt: Elide long strings in their middle in the Peers tab (Hennadii Stepanov)

Pull request description:

  The eliding of long addresses (Onion v3 etc) in the Peers tab in their middle was [discussed](bitcoin-core/gui#262 (comment)) in dashpay#262.

  On master (f0fa324):
  ![DeepinScreenshot_select-area_20210410141435](https://user-images.githubusercontent.com/32963518/114267903-24eea400-9a07-11eb-8c80-99f68d5cc522.png)

  With this PR:
  ![DeepinScreenshot_select-area_20210410140430](https://user-images.githubusercontent.com/32963518/114267796-83675280-9a06-11eb-921f-ca47c2075496.png)

  This PR suggests the minimal diff to achieve the goal. OTOH, this change in behavior is common for all columns in the Peers table, but it seems harmless.

ACKs for top commit:
  jarolrod:
    tACK 4e06133
  promag:
    Code review ACK 4e06133.

Tree-SHA512: 1d5a62afb1152029e69fccea2ae53dcb262a91724a5c03dfc4de8c409b280814d0c211c2f9a71f1a6e927f4ed571ba4ac311de9de8ebb797eaf1051674241bdb
PastaPastaPasta pushed a commit to PastaPastaPasta/dash that referenced this issue Oct 21, 2021
… Peers tab

4e06133 qt: Elide long strings in their middle in the Peers tab (Hennadii Stepanov)

Pull request description:

  The eliding of long addresses (Onion v3 etc) in the Peers tab in their middle was [discussed](bitcoin-core/gui#262 (comment)) in dashpay#262.

  On master (f0fa324):
  ![DeepinScreenshot_select-area_20210410141435](https://user-images.githubusercontent.com/32963518/114267903-24eea400-9a07-11eb-8c80-99f68d5cc522.png)

  With this PR:
  ![DeepinScreenshot_select-area_20210410140430](https://user-images.githubusercontent.com/32963518/114267796-83675280-9a06-11eb-921f-ca47c2075496.png)

  This PR suggests the minimal diff to achieve the goal. OTOH, this change in behavior is common for all columns in the Peers table, but it seems harmless.

ACKs for top commit:
  jarolrod:
    tACK 4e06133
  promag:
    Code review ACK 4e06133.

Tree-SHA512: 1d5a62afb1152029e69fccea2ae53dcb262a91724a5c03dfc4de8c409b280814d0c211c2f9a71f1a6e927f4ed571ba4ac311de9de8ebb797eaf1051674241bdb
pravblockc pushed a commit to pravblockc/dash that referenced this issue Nov 18, 2021
… Peers tab

4e06133 qt: Elide long strings in their middle in the Peers tab (Hennadii Stepanov)

Pull request description:

  The eliding of long addresses (Onion v3 etc) in the Peers tab in their middle was [discussed](bitcoin-core/gui#262 (comment)) in dashpay#262.

  On master (f0fa324):
  ![DeepinScreenshot_select-area_20210410141435](https://user-images.githubusercontent.com/32963518/114267903-24eea400-9a07-11eb-8c80-99f68d5cc522.png)

  With this PR:
  ![DeepinScreenshot_select-area_20210410140430](https://user-images.githubusercontent.com/32963518/114267796-83675280-9a06-11eb-921f-ca47c2075496.png)

  This PR suggests the minimal diff to achieve the goal. OTOH, this change in behavior is common for all columns in the Peers table, but it seems harmless.

ACKs for top commit:
  jarolrod:
    tACK 4e06133
  promag:
    Code review ACK 4e06133.

Tree-SHA512: 1d5a62afb1152029e69fccea2ae53dcb262a91724a5c03dfc4de8c409b280814d0c211c2f9a71f1a6e927f4ed571ba4ac311de9de8ebb797eaf1051674241bdb
gades pushed a commit to cosanta/cosanta-core that referenced this issue May 9, 2022
… Peers tab

4e06133 qt: Elide long strings in their middle in the Peers tab (Hennadii Stepanov)

Pull request description:

  The eliding of long addresses (Onion v3 etc) in the Peers tab in their middle was [discussed](bitcoin-core/gui#262 (comment)) in dashpay#262.

  On master (f0fa324):
  ![DeepinScreenshot_select-area_20210410141435](https://user-images.githubusercontent.com/32963518/114267903-24eea400-9a07-11eb-8c80-99f68d5cc522.png)

  With this PR:
  ![DeepinScreenshot_select-area_20210410140430](https://user-images.githubusercontent.com/32963518/114267796-83675280-9a06-11eb-921f-ca47c2075496.png)

  This PR suggests the minimal diff to achieve the goal. OTOH, this change in behavior is common for all columns in the Peers table, but it seems harmless.

ACKs for top commit:
  jarolrod:
    tACK 4e06133
  promag:
    Code review ACK 4e06133.

Tree-SHA512: 1d5a62afb1152029e69fccea2ae53dcb262a91724a5c03dfc4de8c409b280814d0c211c2f9a71f1a6e927f4ed571ba4ac311de9de8ebb797eaf1051674241bdb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UI All about "look and feel" UX All about "how to get things done"
Projects
None yet
Development

No branches or pull requests

2 participants