Displaying expanded schema when the schema is not started

Issue #5 new
Neuralysys repo owner created an issue

Displaying an expanded schema when its execution has not been started works. However, if changing schema selection and displaying a second exapanded schema (still without starting it) generates the following traceback:

Traceback (most recent call last): File "C:\Users\oreichri\Dropbox\code\EEGAnalyzer\EEGAnalyzer\widgets\schemaView.py", line 266, in drawSchema

startBlock = self.register.getBlock(schemaStartBlock.ID) File "C:\Python27\lib\site-packages\PyBlockWork\registerWrapper.py", line 54, in getBlock

blockString = self.registerExec(Register.getBlockString, blockID) File "C:\Python27\lib\site-packages\PyBlockWork\registerWrapper.py", line 144, in registerExec

return warehouse.proxy(self.registerName).getBlockString(args[0]) File "C:\Python27\lib\site-packages\pyro4-4.22-py2.7.egg\Pyro4\core.py", line 160, in call

return self.__send(self.__name, args, kwargs) File "C:\Python27\lib\site-packages\pyro4-4.22-py2.7.egg\Pyro4\core.py", line 324, in _pyroInvoke

raise data ValueError: The block with ID a260ba51-7592-11e3-8d71-50465d70503e has not been registered.

+--- This exception occured remotely (Pyro) - Remote traceback:

| Traceback (most recent call last): | File "C:\Python27\lib\site-packages\pyro4-4.22-py2.7.egg\Pyro4\core.py", line 753, in handleRequest

| data=method(vargs, *kwargs) # this is the actual method call to the Pyro object | File "C:\Python27\lib\site-packages\PyBlockWork\register.py", line 237, in getBlockString

| raise ValueError("The block with ID " + ID + " has not been registered.") | ValueError: The block with ID a260ba51-7592-11e3-8d71-50465d70503e has not been registered.

+--- End of remote traceback

Comments (2)

  1. Log in to comment