-
Notifications
You must be signed in to change notification settings - Fork 0
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
Comments
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 |
It's regtestnet, but in 0.9 it shows "testnet" instead of "regtest". |
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 |
Here is a testnet transaction with that sizes: 852baf404a70f6d194264c226b923040ca33945e30d5dfa5c28e877a6d83938e (still unconfirmed at the moment) But sounds good for now. :) |
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 :) |
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. |
Leaving open to consider wrapping in next version. |
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. |
There is a value |
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. |
This is already tagged as a 0.0.9.2 improvement now mate :) |
Logging: fix reuse of fReopenDebugLog flag
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.
The text was updated successfully, but these errors were encountered: