Closed GoogleCodeExporter closed 9 years ago
(Note, the exception occurring on line 79 is for rc-2 AFAICT, the previous
version had the error on line 81
according to the log.)
Original comment by follower@gmail.com
on 29 Jun 2009 at 12:53
Screen shot attached. I notice that it mentions there is "No machine currently
connected" but if that's displayed
how is line 79 even executed?.
Original comment by follower@gmail.com
on 29 Jun 2009 at 1:00
Attachments:
Okay, so, my theory of the cause is:
* 'DriverBaseImplementation' has a 'Version' property 'version' which is
initially 'null'.
* 'NullDriver' does not replace the version property.
* 'Version' has a method 'compareTo' which does not handle being passed a
'null' value.
Original comment by follower@gmail.com
on 29 Jun 2009 at 1:35
The following patch seems to "fix" the issue:
Index: src/replicatorg/app/drivers/NullDriver.java
===================================================================
--- src/replicatorg/app/drivers/NullDriver.java (revision 363)
+++ src/replicatorg/app/drivers/NullDriver.java (working copy)
@@ -35,6 +35,8 @@
super();
speedup = 10;
+
+ version = new Version(0,0);
}
public void loadXML(Node xml) {
I have no idea if that's the best approach or not.
But it seems the NullDriver may not be handled well in general as it doesn't
have a presence in the
"Machine>Driver" menu and selecting "Machine>Control Panel" crashes (report to
be added).
Perhaps it would be better to default to the simulator driver rather than a
NullDriver? After all, my reason for
running the application without configuration was to see how the simulation
worked since I didn't have a
machine.
Original comment by follower@gmail.com
on 29 Jun 2009 at 2:14
The NPE is now fixed in SVN, but it's almost certainly not fatal. I'll try to
reproduce this in a few hours when I finally get access to a Mac.
Original comment by pho...@gmail.com
on 29 Jun 2009 at 2:41
I can confirm that I can now update & rebuild SVN and the NPE no longer occurs
AFAICT.
Original comment by follower@gmail.com
on 29 Jun 2009 at 3:12
Thanks for confirming that; appears to be fixed after refactor in 0005.
Original comment by pho...@gmail.com
on 22 Jul 2009 at 10:28
Original issue reported on code.google.com by
follower@gmail.com
on 29 Jun 2009 at 12:49