Pages:
Author

Topic: [XMR] MoneroX - A cross platform graphical account manager for Monero - page 8. (Read 88596 times)

sr. member
Activity: 264
Merit: 250
Update: I tested it running the daemon locally, sending you ~3 Moneroj at a mix in of 0, and it sent the first transaction. I tried sending you ~3 more, and it froze on this second transaction. This, along with my previous post, seems to rule out both a mix in issue, and any issue of using a remote daemon. What should we test next to figure out the true cause?

I've written a private message to you in order to let us discuss the issue in details.
legendary
Activity: 1762
Merit: 1011
Update: I tested it running the daemon locally, sending you ~3 Moneroj at a mix in of 0, and it sent the first transaction. I tried sending you ~3 more, and it froze on this second transaction. This, along with my previous post, seems to rule out both a mix in issue, and any issue of using a remote daemon. What should we test next to figure out the true cause?
legendary
Activity: 1762
Merit: 1011
Wow, I just tested it, and I don't know how, but that *finally* solved the slow balance and transaction loading! It loads these almost immediately now!

However, it *doesn't* seem to have solved the freezing issue on the second transaction. I just tried sending you $3 worth of Moneroj, split into two transactions. The first one went through. The second one froze, exactly the same as before. I'll leave it open to see if it eventually crashes. Btw, I'm using a mix count of 1, if that matters.

Edit: I let it sit for almost two hours, and it never crashed, so I forced closed simplewallet, and that caused the GUI to crash.

Thanks for your feedback and donation! Smiley

Today, I was working on the API more than on the GUI, and I have only tested TXes with a mix count of 0. As  sending 0 mixin transactions consecutively worked fine for me, I suspect that the fault may be in the core application, or I just simply handle the mix count parameter wrong. I'll continue hunting for this bug tomorrow, and will also speak about the case to the core developers if necessary.

I just tried sending you a single transaction with a mix count of zero and it still froze. Sad  I'm going to go back to using the localhost instead of node.moneroclub.com and see if that has any effect.
hero member
Activity: 798
Merit: 500
Nice too see your coding spirit Wink
sr. member
Activity: 264
Merit: 250
Wow, I just tested it, and I don't know how, but that *finally* solved the slow balance and transaction loading! It loads these almost immediately now!

However, it *doesn't* seem to have solved the freezing issue on the second transaction. I just tried sending you $3 worth of Moneroj, split into two transactions. The first one went through. The second one froze, exactly the same as before. I'll leave it open to see if it eventually crashes. Btw, I'm using a mix count of 1, if that matters.

Edit: I let it sit for almost two hours, and it never crashed, so I forced closed simplewallet, and that caused the GUI to crash.

Thanks for your feedback and donation! Smiley

Today, I was working on the API more than on the GUI, and I have only tested TXes with a mix count of 0. As  sending 0 mixin transactions consecutively worked fine for me, I suspect that the fault may be in the core application, or I just simply handle the mix count parameter wrong. I'll continue hunting for this bug tomorrow, and will also speak about the case to the core developers if necessary.
legendary
Activity: 1762
Merit: 1011

Thank you very much for the support! I've just tried sending 3 transactions (2 with a payment ID, and one without any additional information) in a row from my client, and it seemed to be working perfectly: all of them have arrived. But after waiting for a little while, Visual Studio's debugger has notified me that the object responsible for storing the list of transactions was modified from a wrong thread (not the main one), thus, resulting in a crash. Shortly, this was just a side-effect of the migration to the separated API, but I've resolved it already.

Other than that, your crash seems to be related to the RPC communication, as I've set network timeouts for RPC requests to infinite (in order not to experience crashes when trying to save the blockchain, as it takes more than 100 seconds to do so)...

EDIT: v0.41.1 is out now, it should resolve some issues! Wink

Wow, I just tested it, and I don't know how, but that *finally* solved the slow balance and transaction loading! It loads these almost immediately now!

However, it *doesn't* seem to have solved the freezing issue on the second transaction. I just tried sending you $3 worth of Moneroj, split into two transactions. The first one went through. The second one froze, exactly the same as before. I'll leave it open to see if it eventually crashes. Btw, I'm using a mix count of 1, if that matters.

Edit: I let it sit for almost two hours, and it never crashed, so I forced closed simplewallet, and that caused the GUI to crash.
legendary
Activity: 1428
Merit: 1001
getmonero.org
Very nice work Jojatekok! Sent a small donation. I am not using a GUI, command line is fine now that i am used to it after months of using it Tongue ,  but you are constantly trying to improve it and i am impressed Smiley Thank you!
sr. member
Activity: 264
Merit: 250
legendary
Activity: 1762
Merit: 1011
Jojatekok, I'm now using http://node.moneroclub.com with port set to 8880, and it seems to be working. So, I thought I'd try sending you a tip. First shot, I accidentally tipped you around 4 cents worth of Moneroj, which did go through, though! So, I then tried to send you a little more, and, after clicking Send, the client locked up (but didn't crash), and the Send button became stuck, highlighted in blue, and the entire UI was unresponsive, but still would paint. Looking at the simplewallet log, the RPC outputs for both transactions were there, but the second transaction's outputs never concluded with "Transaction successfully sent" -- it seems to have just become stuck before that.  I'm also not seeing any CPU activity from either simplewallet or MoneroClient. I may have to kill the processes manually, it seems.

Edit: after waiting about 45 minutes, MoneroClient finally crashed with the following crash log:

Code:
One or more errors occurred.
   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
   at Jojatekok.MoneroAPI.RpcUtilities.RpcWebClient.PostString(String host, UInt16 port, String relativeUrl, String postData)
   at Jojatekok.MoneroAPI.RpcUtilities.RpcWebClient.HttpPostData[T](String host, UInt16 port, String command, JsonRpcRequest jsonRpcRequest)
   at Jojatekok.MoneroAPI.RpcManagers.BaseRpcManager.HttpPostData[T](String command, JsonRpcRequest jsonRpcRequest)
   at Jojatekok.MoneroAPI.RpcManagers.DaemonRpcManager.QueryNetworkInformation()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.TimerQueueTimer.CallCallback()
   at System.Threading.TimerQueueTimer.Fire()
   at System.Threading.TimerQueue.FireNextTimers()
legendary
Activity: 1762
Merit: 1011

  • Added a way to use remote processes: From now, you are not obeyed to host your own daemon instance, but can rely on an open node. This results in a much lower overall memory footprint on your system, thus, the application should cause no more losses in computing performance

Dude, you are awesome! Btw, it should say "you are not *required* to host your own daemon" rather than "obeyed".  I will test it and donate soon!
sr. member
Activity: 264
Merit: 250


Breaking news!
(No, it's not yet another ordinary release Wink)

Monero Client v0.41.0 has just been released! With the separation of my API and GUI integration of Monero Core's RPC functions, I was able to successfully distinct process and network communication management, thus, resulting in a long-anticipated feature added to the client. Let me present the changelog of today's new release:

  • Added a way to use remote processes: From now, you are not obeyed to host your own daemon instance, but can rely on an open node. This results in a much lower overall memory footprint on your system, thus, the application should cause no more losses in computing performance

    How to use a remote daemon?
    • First, you need to look for an open node which can be used as a reliable remote server (for example: node.moneroclub.com:8880)
    • After that, open Monero Client .NET, and then select Settings -> Options -> Network from the menu
    • Paste the information of the selected node as seen on the image below:

  • Enabled the usage of proxies
  • Balances in the 'Send coins' tab are now selectable
  • Fixed a bug which prevented the account data files from saving



Please consider donating to one of the addresses in my signature if you like this update or want to support further development.
legendary
Activity: 1762
Merit: 1011
Feature request: Please add a date column to the transactions list. Smiley

I'll add support for that as soon as I can retrieve it from the core RPC.

Until then, here is an update I've just posted on the #monero-dev IRC channel:

Quote
[17:32] hi
[17:33] I've decided to try porting Monero API .NET to a PCL (portable class library) project
[17:33] thus, it could run on Linux (Mono .NET), Windows Store apps, XBox, and whatever
[17:33] even on phones
[17:34] that way, real mobile wallet applications could be written in Xamarin in the future Smiley
[17:34] (including Windows Phone, iOS, and Android too!)
[17:35] but this means that assembly management (exe file loading and closing) has to be put in a separate package
[17:35] thus, providing convenience for PC app developers
[17:35] basically, a single API could just cover every platform Smiley
[17:36] thus, providing a new era for Monero application development Cheesy
[17:36] it will take some time to execute all the porting, but has just started
[17:36] and I'll be working on the project every time I have some spare time Wink
[17:37] I would like to ask the core devs to provide RPC commands for everything (including wallet file creation)
[17:38] thus, GUI development could be separated from core dev even in the future

Thanks! Keep up the great work!
sr. member
Activity: 264
Merit: 250
Feature request: Please add a date column to the transactions list. Smiley

I'll add support for that as soon as I can retrieve it from the core RPC.

Until then, here is an update I've just posted on the #monero-dev IRC channel:

Quote
[17:32] hi
[17:33] I've decided to try porting Monero API .NET to a PCL (portable class library) project
[17:33] thus, it could run on Linux (Mono .NET), Windows Store apps, XBox, and whatever
[17:33] even on phones
[17:34] that way, real mobile wallet applications could be written in Xamarin in the future Smiley
[17:34] (including Windows Phone, iOS, and Android too!)
[17:35] but this means that assembly management (exe file loading and closing) has to be put in a separate package
[17:35] thus, providing convenience for PC app developers
[17:35] basically, a single API could just cover every platform Smiley
[17:36] thus, providing a new era for Monero application development Cheesy
[17:36] it will take some time to execute all the porting, but has just started
[17:36] and I'll be working on the project every time I have some spare time Wink
[17:37] I would like to ask the core devs to provide RPC commands for everything (including wallet file creation)
[17:38] thus, GUI development could be separated from core dev even in the future
legendary
Activity: 1762
Merit: 1011
Feature request: Please add a date column to the transactions list. Smiley
newbie
Activity: 49
Merit: 0
Thanks for all the feedback provided! Right now, I'm working on fully separating the API part from the GUI, thus, I've created a new GitHub repository for Monero API .NET, which could be used by merchant services to easily utilize Monero core functions from the Microsoft .NET programming languages.

I've just gone on a 1-week holiday, though, but will try to continue the developments as soon as I have time (for instance, airplanes are perfect places for this task Smiley).

Github project looks good!
sr. member
Activity: 264
Merit: 250
Thanks for all the feedback provided! Right now, I'm working on fully separating the API part from the GUI, thus, I've created a new GitHub repository for Monero API .NET, which could be used by merchant services to easily utilize Monero core functions from the Microsoft .NET programming languages.

I've just gone on a 1-week holiday, though, but will try to continue the developments as soon as I have time (for instance, airplanes are perfect places for this task Smiley).
newbie
Activity: 49
Merit: 0
Thank you for your hard work! It works very great!
newbie
Activity: 17
Merit: 0
Yes works awesomely! Thanks mate for your work on this  Grin

Btw, one helpful thingie for us non-computer-pros would be the instructions for a clean-install. what folders and where to delete etc.
hero member
Activity: 658
Merit: 503
Monero Core Team
sr. member
Activity: 264
Merit: 250
The crash log message still says the same. simplewallet was in place and i used it to create a wallet just in case that would help, but no, but this time it allowed me to open the backup while initializing but it still crashed in 2 minutes with the same crash log message.

It sounds weird that you were able to successfully create a new account, then, as this surely is an assembly location problem...

Please try removing Monero Client .NET's folder from '%LocalAppData%\Jojatekok' before starting the application next time. If that doesn't solve your issue, I'll think about other causes. Wink
Pages:
Jump to: