| Error while connecting two components with mouse (org.eclipse.rcptt.tesla.gef) [message #1742586] |
Mon, 05 September 2016 14:42 |
 Oguz Yildirim
Messages: 1
Registered: May 2016 |
Junior Member |
|
|
An unhandled exception error is observed while connecting two blocks inside the AUT, using mouse-move function of RCPTT:
This error does not happen during normal usage of the software. The error happens at the point when Ethernet and FORTE_PC function blocks were tried to be connected with each other, as seen in the screenshot at this link:
https://www.eclipse.org/4diac/documentation/html/tutorials/img/flipFlop_deviceDefinition.png
while running the beginning parts of the tutorial given at this address:
https://www.eclipse.org/4diac/documentation/html/tutorials/flipFlop_tutorial.html
as a test case. This was a tutorial for an older version of the AUT, in the new one, FORTE_PC is used instead of RMT_DEV.
What is more, while using the old version of the AUT, this error was not observed. It was encountered in the newer version.
This most recent version of the AUT can only be built from source from the website of fordiac,
http://hg.code.sf.net/p/fordiac/fordiac-ide
Since this version is not available online.
Or to make things easier I can present an already built one of this version of the AUT, given at this address, which is for windows 64-bit platform:
https://www.dropbox.com/s/m89s3a2n2k5qt6q/4DIAC-IDE.zip?dl=0
To reproduce the error, if the test script which caused this error is required, it can be found at the attachment along with two contexts which clean the workspace and opens the desired perspective. Moreover, the aut/.metadata/.log file can also be found at the attachment.
In addition to this error, if this test is run, and if it is desired to be run again, sometimes during the execution of the contexts to clean the workspace, another unhandled exception error occurs.
To prevent that, I wrote an ecl script which deletes the opened projects from the workspace, however it would be nice not to require an ecl script context for that since we have a workspace context.
Since these errors do not occur during the normal usage of the AUT, I thought that there could be a possible bug in this case or something that I did not realize, therefore I kindly ask for help.
Sorry for the long summary but thought I would rather explain everything in detail. If you need further information please just tell me.
Regards,
Oguz
[Updated on: Wed, 14 September 2016 10:14] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.02835 seconds
] 
Search
Help
Register
Login
Home
