Hi guys,

 

On my setup Brickv happily starts up with an enabled Connect button. But when I press it, it moans to me that brickd probably isn't running (it isn't, since it just crashes all the time).

 

A cleaner, more user-friendly approach is to only enable the Connect button **after** brickv itself checked whether brickd is running or not. This is a less frustrating approach... and doesn't violate a classic UI design guideline: "don't allow the user to perform ANY operation which the program itself can know in advance will fail".

 

When brickv sees that brickd isn't running, it could also "annotate" or "decorate" the Connect button (which is disabled) with a little friendly remark like "No brickd running".

 

Hope this helps,

 

  Laurence

 

Which IP should brickv use to test it? We can't disable the connect button, since we don't know which IP you want to connect to .

If the Host and Port fields are filled in, as they are when Brickv is launched out-of-the-box, then you have all the info you need.