Quote from: extro24 on February 16, 2014, 12:11:13 PM

Quote from: Pompobit on February 16, 2014, 02:56:42 AM

-I also included the change proposed by exe here: https://bitcointalk.org/index.php?topic=435170.msg5107703#msg5107703

The windows client is out, you can download it here : http://www.mediafire.com/download/e49da4ni8t4eru4/imp_huntercoin.zip
The source code is here: https://github.com/pompobit/huntercoin

Thanks Pompobit! Especially thank you for adding your own branch of the client to Github. Huntercoin is going to be BIG, and I foresee hundreds of developers. I suspect that a lot of the Worldforge people will also join Huntercoin. They had no money to motivate them, but that has changed with cryptocurrencies. There is a lot of the Worldforge 3D media which could be merged into Huntercoin.

The Flushing wallet.dat delay (about 30 seconds) was one easy problem to get rid of. But the following operations all delay Qt:

askfor tx
askfor block
sending getdata
received getdata
AcceptToMemoryPool

If you run the client in Qt Creator after compiling and check the Window->Output Panes->Compile Output window you will see how these operations freeze the client. As the number of players have increased, the client has become unusable again.

The Qt developers recommend injecting

Code:

qApp->processEvents()

into loops with long disk operations. You must also

Code:

#include

to be able to call qApp. That is what I have been trying to do in main.cpp, but there might be other places in the code with disk operations.

MithrilMan is using threads. He doesn't have a branch on Github and it may not be necessary to go that far. I'm hoping that it will be easier to ungum the knots with processEvents().

oh, sorry for have reported your name wrong, I remembered exo Tongue