Im on RC2 and it shows the median at the top which is nice. Still would be even better to show it on the graph as well.

The overlapping has now stopped, I cant figure out if that is because of the new median-limit rule, or if its because the demand for BitUSD has increased.

Quote from: tonyk on September 03, 2014, 10:17:22 PM
First a question. Is the bitBTC:bitUSD going to have feed based median price?

If yes, it  now shows:

Median Price
31.1896
BitBTC/BitUSD

No price feed for that pair, that is a GUI bug. 

First a question. Is the bitBTC:bitUSD going to have feed based median price?

If yes, it  now shows:

Median Price
31.1896
BitBTC/BitUSD

Quote from: bytemaster on September 03, 2014, 09:26:27 PM
I have asked DAC Sun to produce a Windows 64 bit version.  The crypto is 2x faster in 64 bit.

I will give it a go when this happens

upgraded to 0.4.11-rc2.
GUI
Win 7 /32 bit

Still hangs up in the first ever attempt to close the app.
This has been the case on Win and Ubuntu for the last 2-3 releases.


[RESOLVED in 0.4.12]!!!
The difference is that at least now with  0.4.11-rc2 , the force close, does not leave any btsx processes running.

RC2 is working well as expected. It's nice seeing blocks coming through with multiple transactions.

I have asked DAC Sun to produce a Windows 64 bit version.  The crypto is 2x faster in 64 bit.

Is win binary coming shortly, or my time is better spent upgrading linux to RC2 ?

Ok I see the win version is up.

RC2 released: https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.11-RC2

More market fixes so RC1 users still will have to upgrade.

Upgraded delegate node to 0.4.11-rc1 yesterday. Running well so far.

upgraded to 0.4.11-rc2.

'display bug' partly fixed?!?

First off, I am probably not running the very last 0.4.11 version as I installed it last night (US time zones),
>> about

{
  "bitshares_toolkit_revision": "cfad07c39a1cc56b67b8715721e5aaba60a67611",
  "bitshares_toolkit_revision_age": "21 hours ago",
  "fc_revision": "a0b3a9a92d28ec0b3a08b45b8c1449737f56dd34",
  "fc_revision_age": "24 hours ago",
  "compile_date": "compiled on Sep  3 2014 at 00:09:09"
}

But the order amounts now refresh/change to the correct remaining (as opposed to initial) amount.
The same can not be said about the order book? Getting 'out' and back 'in', of this particular assets screen, seem to do the refreshing... but  only for the ask side of the order book.  8)

build and client running without issues so far.  +5%

delegate.bitder updated to 0.4.11-RC1.  No problems so far.

Edit: updated to 0.4.11-RC2. No problems so far.

It appears the Windows 0.4.11 RC did not pull in the changes to the GUI.   I will let DAC Sun know so they can rebuild it.   Thanks for help testing.

active delegates spartako,spartako1,spartako2 updated to 0.4.11-RC1 without problem:


default (unlocked) >>> getinfo
{
  "blockchain_head_block_num": 389578,
  "blockchain_head_block_age": "9 seconds old",
  "blockchain_head_block_timestamp": "2014-09-03T13:39:20",
  "blockchain_average_delegate_participation": "100.00 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_accumulated_fees": "315,234.67322 BTSX",
  "blockchain_delegate_pay_rate": "2.60610 BTSX",
  "blockchain_share_supply": "1,999,913,503.33380 BTSX",
  "blockchain_blocks_left_in_round": 80,
  "blockchain_next_round_time": "at least 13 minutes in the future",
  "blockchain_next_round_timestamp": "2014-09-03T13:52:40",
  "blockchain_random_seed": "619790d36101e5d5fdf93739f4c69f06ba4332c3",
  "client_data_dir": "/home/spartako/.BitSharesX",
  "client_version": "0.4.11",
  "network_num_connections": 11,
  "network_num_connections_max": 30,
  "ntp_time": "2014-09-03T13:39:29",
  "ntp_time_error": -0.0025490000000000001,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "31 years  in the future",
  "wallet_unlocked_until_timestamp": "1910-04-06T08:48:37",
  "wallet_last_scanned_block_timestamp": "2014-07-24T09:23:30",
  "wallet_scan_progress": "? %",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": "6 minutes in the future",
  "wallet_next_block_production_timestamp": "2014-09-03T13:45:30"
}