Topic: MultiBit - page 63. (Read 336309 times)
Thanks - I have added it in with a tick for Lion and a question mark for Mountain Lion. Let me know if it is happy with Mountain Lion when you install it.
That is a good site.
I am on 'one of the leopards' on my Mac laptop - cannot remember which.
MultiBit just needs Java 6 or higher but can anyone definitely confirm it works on Lion and Mountain Lion ?
I will then add it in.
I works on Lion for sure. I am waiting a few days to update to Mt. Lion. I am on 'one of the leopards' on my Mac laptop - cannot remember which.
MultiBit just needs Java 6 or higher but can anyone definitely confirm it works on Lion and Mountain Lion ?
I will then add it in.
That is a good site.
I am on 'one of the leopards' on my Mac laptop - cannot remember which.
MultiBit just needs Java 6 or higher but can anyone definitely confirm it works on Lion and Mountain Lion ?
I will then add it in.
I am on 'one of the leopards' on my Mac laptop - cannot remember which.
MultiBit just needs Java 6 or higher but can anyone definitely confirm it works on Lion and Mountain Lion ?
I will then add it in.
Mac OS X 10.8 (Mountain Lion) is out and I think MultiBit and Satoshi Bitcoin-Qt application should be on the list
http://roaringapps.com/apps:table
http://roaringapps.com/apps:table
I have got the encrypted wallet load and save working now.
I.E. you can password protect a wallet, save it and it gets loaded up properly.
Lots more testing etc to do on it but that is progress.
I.E. you can password protect a wallet, save it and it gets loaded up properly.
Lots more testing etc to do on it but that is progress.
Thanks - it is pretty old school yes. :-)
I find it quite useful as it picks up quirks here and there. If they are not critical I will ship it anyhow but it gives me an idea of areas where some more work is needed.
I find it quite useful as it picks up quirks here and there. If they are not critical I will ship it anyhow but it gives me an idea of areas where some more work is needed.
Great checklist! Old school on paper works too!
There is a new release of MultiBit at:
http://multibit.org
Version 0.4.5
Enhancements:
+ Faster connection to the Bitcoin network at startup
+ More help on 'Available to spend'
Scan of release checklist
http://multibit.org
Version 0.4.5
Enhancements:
+ Faster connection to the Bitcoin network at startup
+ More help on 'Available to spend'
Scan of release checklist
I have tweaked the message users get when they try send bitcoin but do not have enough available to spend.
They now get the message:
If they click on the 'More Help' button they get shown the help for "What does 'Available to spend' mean ?":
http://multibit.org/postImages/availableToSpend.png
They now get the message:
If they click on the 'More Help' button they get shown the help for "What does 'Available to spend' mean ?":
http://multibit.org/postImages/availableToSpend.png
I will start using the #multibit channel on irc.freenode.net
Hi Jim,
Idunno forums to me feel 'official' whereas irc feels more 'apropos' (?) I tend to be on irc always so it's like second nature to me,
to have quick conversations.
I guess I prefer chatting over writing official document
Idunno forums to me feel 'official' whereas irc feels more 'apropos' (?) I tend to be on irc always so it's like second nature to me,
to have quick conversations.
I guess I prefer chatting over writing official document
I have been investigating the long time it takes to get from "Connecting..." to "Online" in the last couple of versions.
This is due to a couple of the default hosts used in the initial DNS lookup being offline.
I have changed how it does the lookup so that it tries the 'good' hosts first and then only tries the 'possible' hosts if it is desperate.
On my machine that cuts the connect time down to around 15 seconds (which is about what it used to be).
The fix will go into the next production release (v0.4.5) which will probably be on Monday.
This is due to a couple of the default hosts used in the initial DNS lookup being offline.
I have changed how it does the lookup so that it tries the 'good' hosts first and then only tries the 'possible' hosts if it is desperate.
On my machine that cuts the connect time down to around 15 seconds (which is about what it used to be).
The fix will go into the next production release (v0.4.5) which will probably be on Monday.
@xorgate
p.s. I was just wondering why you recommend having a multibit irc channel ?
I ask because there is already this thread, messaging and email (on the multibit.org site) as possible contact methods.
Do you find it more productive?
p.s. I was just wondering why you recommend having a multibit irc channel ?
I ask because there is already this thread, messaging and email (on the multibit.org site) as possible contact methods.
Do you find it more productive?
Since I am trying out multibit, I sent 1 btc to it in 1 tx.
Then I used multibit to send 0.1xxx btc to another address. Now, I cannot send another tx,
the client tells me there are not enough funds. This is confusing because there are at least 0.8xxxx btc in the wallet.
The message (translated) contains 'Important: you can only spend confirmed bitcoins'.
(This was written when the last block was 189983 which was created 45 minutes ago)
(Tip: have an irc channel)
Then I used multibit to send 0.1xxx btc to another address. Now, I cannot send another tx,
the client tells me there are not enough funds. This is confusing because there are at least 0.8xxxx btc in the wallet.
The message (translated) contains 'Important: you can only spend confirmed bitcoins'.
(This was written when the last block was 189983 which was created 45 minutes ago)
(Tip: have an irc channel)
Hi ErebusBat,
The google zebra-crossing library (zxing) is very good for reading QR codes. (I use it already). The problem with a general scan solution is camera support. There are too many different sorts of camera on various platforms.
You can imagine:
'I have a OEM Logitech 933 scanner hooked up via wifi to a Windows Vista machine and your software does not work.'
That's a semi-infinite task I would not want to do if being paid, nevermind for free.
:-)
Jim
Good point.The google zebra-crossing library (zxing) is very good for reading QR codes. (I use it already). The problem with a general scan solution is camera support. There are too many different sorts of camera on various platforms.
You can imagine:
'I have a OEM Logitech 933 scanner hooked up via wifi to a Windows Vista machine and your software does not work.'
That's a semi-infinite task I would not want to do if being paid, nevermind for free.
:-)
Jim
I had assumed that the library would abstract the camera out (like any supported windows imaging supported camera)
Hi ErebusBat,
The google zebra-crossing library (zxing) is very good for reading QR codes. (I use it already). The problem with a general scan solution is camera support. There are too many different sorts of camera on various platforms.
You can imagine:
'I have a OEM Logitech 933 scanner hooked up via wifi to a Windows Vista machine and your software does not work.'
That's a semi-infinite task I would not want to do if being paid, nevermind for free.
:-)
Jim
The google zebra-crossing library (zxing) is very good for reading QR codes. (I use it already). The problem with a general scan solution is camera support. There are too many different sorts of camera on various platforms.
You can imagine:
'I have a OEM Logitech 933 scanner hooked up via wifi to a Windows Vista machine and your software does not work.'
That's a semi-infinite task I would not want to do if being paid, nevermind for free.
:-)
Jim
In the latter case you would probably want to delete the key out the wallet entirely for more security (once you have checked it has printed ok, obviously).
This got me thinking.... it would be nice to have a verify function, where you could scan the bill and MultiBit would give you a go/no-go if it could read+decode the bill.Obviously this would depend on a suitable QR scanning library being available
Previously in MultiBit there have been three sorts of testing done:
1) Unit tests. This is low level code testing.
2) Functional tests to check things like replaying from the genesis block. You do everything for real i.e. connect to the network and actually download blocks.
3) Manual testing on my Mac plus virtual machines (Windows, Linux) against a checklist for each release.
For the encrypted wallet testing I have added a new layer of testing (UI robot testing if you are familiar with it). This is testing at the level of:
etc
They are a bit laborious to write but in combination with the other tests hopefully leave little space for bugs to lurk. (Well, that is the theory!).
You can see an example (for the Export Private Keys) here:
Export Private Keys robot test.
1) Unit tests. This is low level code testing.
2) Functional tests to check things like replaying from the genesis block. You do everything for real i.e. connect to the network and actually download blocks.
3) Manual testing on my Mac plus virtual machines (Windows, Linux) against a checklist for each release.
For the encrypted wallet testing I have added a new layer of testing (UI robot testing if you are familiar with it). This is testing at the level of:
- Action: simulate clicking a particular button.
- Expected response: message saying 'Enter the wallet password'.
- Action: simulate entry of wallet password. click another button
- Expected response: export file written. message saying 'Private keys exported'.
etc
They are a bit laborious to write but in combination with the other tests hopefully leave little space for bugs to lurk. (Well, that is the theory!).
You can see an example (for the Export Private Keys) here:
Export Private Keys robot test.
Jump to: