I have the first beta version for 1.5 ready. I'll put up the full change log on github in the next day or so.

https://github.com/Tranz5/HoboNickels/releases/tag/1.4.7.0

Although I have had no issues, I do highly suggest you take the time (after you shutdown the client) to backup your wallet(s).dat, blk0001.dat and  database/txleveldb directories, before starting up the new client.

Please let me know if you see anything odd or have any issues.

Enjoy!

Like the new S4C addition.  Will I still have to enable S4C every time I start up the wallet? 

I think it's the leftover of the blocks you selected. It's still in your wallet but but a different address. You can avoid this from happening by checking the 'çustom change address' and fill in your regular address.

So don't worry, the coins are still yours!

Your total balance is ok?

Using the explorer (hbn.cryptocoinexplorer.com) can really help in tracing transactions. Click the transaction button and enter the txhash(txid) in the search box and you will get an organized  readout of the transaction with links to all the various input/output transactions and addresses.

To see the balance of the change address:
Open your client and click the help button -> Debug Window and use the command "getbalance EhPUwKk8DT5Rg8JKFkxZzVz7cb3dJVxTVg" You should see the change balance there. It also shows in the ledger for that address at the explorer site. (Click the address ledger button and enter the address)

Just noticed your signature. Cool Address!

How to generate such a cool address??

thanks to all! Errors was in wallet.dat. rescan, salwagewallet and repair didn't fix it, but import/export keys solved problem 

Coin control did't show part of the coins on change addresses, "getbalanse change_address" return 0
After use "repair wallet", coin control started show coins on change addresses, but i could not use these coins and after restart app, didn't show them again

Yes it did help. The thing that I like the best that has changed was the locking scheme. The GUI is a lot more responsive for most operations, like rescan operations.  Which also helps with things like syncing, as the core won't be waiting for the GUI.

On the surface it may see like the gui is less responsive when it comes to syncing, but that is only because the gui will be updated less often, so the time between updates is larger but the jumps in block counts will also be larger.

Anyway thanks for feedback.