Handle high DPI a bit more gracefully on Win32. #277
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Not ideal, icons for send and address book don't show, just the standard bitcoin icon, and balance is still cut off, but the number is readable.
jgarzik
pushed a commit
that referenced
this pull request
May 27, 2011
Handle high DPI a bit more gracefully on Win32.
zathras-crypto
added a commit
to zathras-crypto/omnicore
that referenced
this pull request
Feb 3, 2015
Minor doc changes and fix ver for tag
CodeShark
pushed a commit
to CodeShark/bitcoin
that referenced
this pull request
Jan 18, 2017
add void-main pub key
classesjack
pushed a commit
to classesjack/bitcoin
that referenced
this pull request
Jan 2, 2018
Fixed bytecodeexec_tests and condensingtransaction_tests.
cryptapus
pushed a commit
to cryptapus/bitcoin
that referenced
this pull request
May 3, 2021
32d8d8a Add options argument for name_pending. (Daniel Kraft) 9cf463b Add options argument to name_list. (Daniel Kraft) 5bb8a2e Add options argument for name_show/history. (Daniel Kraft) Pull request description: This adds an optional `options` argument for the remaining name RPCs: `name_show`, `name_history`, `name_list` and `name_pending`, as suggested in bitcoin#194. For now, the only implemented options are `nameEncoding` and `valueEncoding`, allowing to override the default-configured encodings on a per-RPC basis (implementing another missing part of bitcoin#246). Two name-related RPC methods are remaining without an `options` argument, where I suggest to not add it at all: - `namerawtransaction`: This already has many arguments and adding an `options` argument seems not too useful. `namecoin-tx` can already be used instead, which allows to have arbitrary names and values in hex-encoding. - `sendtoname`: This also already has many arguments so adding `options` would make the signature even more complex. Furthermore, this call is "informally deprecated" anyway, see bitcoin#12, and probably not often used. Tree-SHA512: fe9db50986e05c6adc96ccf4dd4baf904a7d88cc19ff043f01613da7da3da818accb7c73083489ff87e6263dee7e615628b3d27081a433b526ac317b4d1f4f72
rajarshimaitra
pushed a commit
to rajarshimaitra/bitcoin
that referenced
this pull request
Aug 5, 2021
* challange -> challenge * deliverd - delivered * more on deliverd - delivered * mallicous -> malicious * aquire -> acquire * one more aquire -> acquire * deposied -> deposited * noone -> no one * desireable -> desireable * commited -> committed * everone -> everyone * btween -> between * shoul -> should * encrtypted -> encrypted * didicated -> dedicated * derrivation -> derivation
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not ideal, icons for send and address book don't show, just the
standard bitcoin icon, and balance is still cut off, but the
number is readable.