11.2 - Dash Release

darkwing said:
VWxzFMO.png

Small bug on mac wallet under transactions the end of the amounts is obscured by the scrollbar.

*I posted this in the wrong thread before I think - apologies if already addressed
Click to expand...

We recently did a change (the arrow-buttons in the scrollbar were missing, see https://github.com/dashpay/dash/pull/304), which might as a side-effect fix this as well, but since I'm lacking a OSX-test-system I don't know. (Windows and Linux do not show this problem).

It's not yet in the official binaries, but if you know how to build a OSX-version from the official master-branch (https://github.com/dashpay/dash) you can test it yourself.

I could build OSX-binaries for you to test if you want, though.
 
I'll give building it a go. I'd like to mess with the skin anyway so I'll need to know that..
 
Last edited by a moderator:
crowning said:
We recently did a change (the arrow-buttons in the scrollbar were missing, see https://github.com/dashpay/dash/pull/304), which might as a side-effect fix this as well, but since I'm lacking a OSX-test-system I don't know. (Windows and Linux do not show this problem).

It's not yet in the official binaries, but if you know how to build a OSX-version from the official master-branch (https://github.com/dashpay/dash) you can test it yourself.

I could build OSX-binaries for you to test if you want, though.
Click to expand...



darkwing said:
VWxzFMO.png

Small bug on mac wallet under transactions the end of the amounts is obscured by the scrollbar.

*I posted this in the wrong thread before I think - apologies if already addressed
Click to expand...


Ok.. got it to compile (after finally realising I had macports and homebrew installed and a lot of computer says no)
And the answer is... it looks the same.

Bug.
 
darkwing said:
Ok.. got it to compile (after finally realising I had macports and homebrew installed and a lot of computer says no)
And the answer is... it looks the same.

Bug.
Click to expand...
Hmm... I can't confirm this. I'm on Mac OS X 10.10.3:
099mQYz.png


Make sure you see "v0.11.2.22-88cd80d-dirty-beta" in "About Dash Core" dialog (should match first few symbols of the latest commit id in master tree on github)
 
UdjinM6 said:
Hmm... I can't confirm this. I'm on Mac OS X 10.10.3:

Make sure you see "v0.11.2.22-88cd80d-dirty-beta" in "About Dash Core" dialog (should match first few symbols of the latest commit id in master tree on github)
Click to expand...

Copied from the about dialogue box:
v0.11.2.22-88cd80d-dirty-beta (64-bit)

So right version but difficult to fix if you can't replicate.
 
darkwing said:
Copied from the about dialogue box:
v0.11.2.22-88cd80d-dirty-beta (64-bit)

So right version but difficult to fix if you can't replicate.
Click to expand...

Would you please have a look in the "About Qt" dialogue which version of Qt you're using?

I plan to buy a Mac for testing (so I don't have to ping poor UdjinM6 each time for testing :wink:) next weekend and may be able to track this one down.
 
crowning said:
Would you please have a look in the "About Qt" dialogue which version of Qt you're using?

I plan to buy a Mac for testing (so I don't have to ping poor UdjinM6 each time for testing :wink:) next weekend and may be able to track this one down.
Click to expand...

I compiled specifying QT5 as I had a look in the DMG and that was what was used there.
 
darkwing said:
I compiled specifying QT5 as I had a look in the DMG and that was what was used there.
Click to expand...
I compiled with 4.8.6 first, recompiled with 5.4.1 now but same here - no bug for me.......
I even cloned from source to the completely new folder and recompiled with qt5 again there.. nothing... :confused:
 
UdjinM6 said:
I compiled with 4.8.6 first, recompiled with 5.4.1 now but same here - no bug for me.......
I even cloned from source to the completely new folder and recompiled with qt5 again there.. nothing... :confused:
Click to expand...

I'd say unless someone else reports it then let's put it down to Gremlins in my machine :)

Thanks for for looking gents.
 
pille said:
Is Darksend™ disabled? I get this all the time:

9o6ag4l3.png


(>2 DASH in wallet)
Click to expand...
No, it doesn't mean Darksend is disabled. It's a vague DS feedback message of what DS is doing... I think DS just submitted a request for mixing but somehow the request is incomplete, the waiting is timed out, and DS is telling you it will resubmit the request... You'll see.
 
I've sent all coins from the multiple addresses I had in my wallet to a new address. Now Darksend mixing started immediately. Before that I've been waiting "forever" and nothing happened.
 
UdjinM6 said:
There are some edge cases when DS might look "stuck", not everything is optimized yet... Working on it :)
Click to expand...
meaby he was mining with p2pool so he had a lot of dust tx ;)
 
pille said:
could it be a problem when the "part"-wallets are to small? for example, before and after sending to the one new address

https://chainz.cryptoid.info/dash/t...080a462dcf1a08f335098b00f0d1e90e248771c37.htm



Thats what I meant lots of small inputs. So it seems to be a problem.
Click to expand...
I think so. I can't remember exactly how Udjin explained this but this is inherited from the bitcoin codebase, something about small inputs aren't important in btc or something like that. It used to be worse when we first switched to the bitcoin core, it took forever for DS to mix and it kept getting "stuck"...

Also, I might be wrong but if you have the coins from mining they're almost like anonymous coins, I was told anonymizing them isn't necessary. UdjinM6 , what do you think?
 
You must log in or register to reply here.
Back
Top