Closed GoogleCodeExporter closed 8 years ago
Fixed in the SVN trunk. (Fix may be obsolete in the 0005 refactor.)
Original comment by pho...@gmail.com
on 29 Jun 2009 at 2:39
AFAICT this fix breaks the simulator as it uses the Null Driver. The original
issue is due to the combination of
an "Unknown"/"Null" machine and the NullDriver. The NullDriver is valid if the
machine is the simulator.
So, my original suggestion had a terminology issue. The default *Machine*
should probably be the simulator
rather than Unknown/Null.
This also suggests the menu item shouldn't actually be "Driver" as you're not
actually selecting the driver,
you're actually selecting the machine?
The error occurs when this sequence of events is logged:
------------
Loading machine: Unknown
No driver config found.
Loading driver: NullDriver
Machine set to replicatorg.app.MachineController@e90097
------------
Which is what happens when there is no preferences file *or* no machine/driver
has been selected since the
preferences file was created.
So, it seems the issue isn't the NullDriver in this case--it's the
"Unknown/null" machine?
I think this change can be reverted and a different approach used.
Original comment by follower@gmail.com
on 29 Jun 2009 at 3:28
The only thing this particular change should alter is the ability to launch the
machine control panel when the simulator is selected. That makes sense to me,
since
the control panel exists to directly control a machine.
I'm not sure what the actual error you're getting now is-- can you be more
specific?
The vocabulary used internally in replicatorg is kind of terrible. I'm in the
middle
of a big refactor right now and one of the first questions I had to address was
whether I was going to restructure the machinecontroller/machinemodel/driver
mess for
0005. I'm probably going to push most of that off for 0006 in the interest of
getting 0005 out this week; it's probably more important in the short term to do
things like get the build threads out of the editor window code. :/
Original comment by pho...@gmail.com
on 29 Jun 2009 at 3:42
Original issue reported on code.google.com by
follower@gmail.com
on 29 Jun 2009 at 2:19