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

UI: Toolbox: wrap property metadata after n characters #24

Open
1 task done
dexX7 opened this issue Feb 15, 2015 · 12 comments
Open
1 task done

UI: Toolbox: wrap property metadata after n characters #24

dexX7 opened this issue Feb 15, 2015 · 12 comments

Comments

@dexX7
Copy link

dexX7 commented Feb 15, 2015

property_long

  • 17) Property metadata should be wrapped

In the best case based on the window size, but this could as well be a feature for the next release. More relevant, in my opinion, is to prevent extreme client sizes as shown above.

In this example maximum character numbers of 255 were used for all metadata fields.

@zathras-crypto
Copy link
Owner

I notice the title says your wallet is running on testnet, but propId 4 is not your created property (are you running regtest and does the wallet still say testnet if running on regtest?).

Thanks
Z

@dexX7
Copy link
Author

dexX7 commented Feb 16, 2015

It's regtestnet, but in 0.9 it shows "testnet" instead of "regtest".

@zathras-crypto
Copy link
Owner

In the best case based on the window size, but this could as well be a feature for the next release. More relevant, in my opinion, is to prevent extreme client sizes as shown above.

I've gone for immediate protection against extreme client sizes, but need to evaluate the impact of wrapping (as it would use more vertical space for the label and force everything below it to be laid out further down - what the impact of this is I'm not 100% yet). I figure protection via truncation will do the job for 0.0.9.1 and then wrapping can be revisited.

Thanks
Z

8f310a1

@dexX7
Copy link
Author

dexX7 commented Feb 16, 2015

Here is a testnet transaction with that sizes: 852baf404a70f6d194264c226b923040ca33945e30d5dfa5c28e877a6d83938e (still unconfirmed at the moment)

But sounds good for now. :)

@zathras-crypto
Copy link
Owner

Awesome thanks - I tested on exploitcoin on mainnet and it does the job for data, I'll check out the other fields with your TX in a sec when it confirms :)

@zathras-crypto
Copy link
Owner

There was a minor issue (now corrected - a841d54) - W is the widest character in non-fixed-width fonts so I think the values are pretty safe for now.
image

@zathras-crypto
Copy link
Owner

Leaving open to consider wrapping in next version.

@dexX7
Copy link
Author

dexX7 commented Feb 16, 2015

Two questions, but I'll give it a shot later myself: could the text be copyable? And could there be a tooltip to show the whole description? I would assume this would be a low hanging fruit.

@dexX7
Copy link
Author

dexX7 commented Feb 16, 2015

Hmm... so this is still larger than the minimal size, as it seems. I mean, it's not really a huge issue, but probably the best of both:

property_min

property_large

@zathras-crypto
Copy link
Owner

There is a value maxLabelWidth that we can reduce if we feel it's too much bigger than minimal size - currently set at 70 chars but can be tweaked - this is primarily a stopgap until we look at a better way to do it in 0.0.9.2 (eg wrapping).

@dexX7
Copy link
Author

dexX7 commented Feb 20, 2015

I suggest to either close this and open another one for an improved version, or tag this one for 0.0.9.2 as well.

@zathras-crypto
Copy link
Owner

This is already tagged as a 0.0.9.2 improvement now mate :)

zathras-crypto pushed a commit that referenced this issue Mar 25, 2015
zathras-crypto added a commit that referenced this issue Apr 24, 2015
Logging: fix reuse of fReopenDebugLog flag
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants