|
Re: 4DIAC 1.13.0 IDE [message #1834765 is a reply to message #1834750] |
Tue, 17 November 2020 13:56 |
|
Hi,
I'm not happy to hear that. Please see some answers below.
NOJA Power wrote on Tue, 17 November 2020 11:16
- The monitor/watch for debugging does not work correctly at times
Can you be more specific what is not working. I have not noticed issues here. Is there any output in the .log file.
NOJA Power wrote on Tue, 17 November 2020 11:16
- Mapping FB to EMB_RES does not work correctly at times
Can you be more specific what is not working. I have not noticed issues here. Is there any output in the .log file.
NOJA Power wrote on Tue, 17 November 2020 11:16
- The linework does not display correctly at times (close/open IDE usually fixes the issue)
Yes we noticed that. We have introduced an automatic layout algorithm with 1.13.0. You can test that by context menu entry layout the diagrams. Unfortunately we haven't yet managed to align the new layouting with the old routing leading sometimes to not so nice results.
NOJA Power wrote on Tue, 17 November 2020 11:16
- The FB code generated from the latest IDE will not compile with C++04 compiler (not a big issue, I can use the old IDE to generate FB changes and we don't need to do this very often)
As posted already we are on our way to enhance 4diac FORTE to more modern C++. We try our best to be backwards compatible and therefore happy for feedback.
NOJA Power wrote on Tue, 17 November 2020 11:16
- Export fboot window is blank and export is not possible
We just recently noticed that we broke this: https://bugs.eclipse.org/bugs/show_bug.cgi?id=568326
Working on it to get it fixed soon.
|
|
|
|
|
Re: 4DIAC 1.13.0 IDE [message #1834792 is a reply to message #1834791] |
Wed, 18 November 2020 05:05 |
NOJA Power Messages: 19 Registered: May 2020 |
Junior Member |
|
|
Hi,
Ok, I managed to get past the last issue. This issue is to do with 'monitor' behaviour. These are the steps I took:
- Continue from last test (previous post)
- Unmap all
- ctrl-a in App tab to select all FB's and map to EMB_RES
- Open EMB_RES, mapping worked
- Enable disable monitoring on EMB_RES tab a few times, add and remove watch from various FB's
- Switch to application tab, no watches are available (which are enabled on EMB_RES tab)
- Enable watches on FB in App tab that already has a watch enabled on EMB_RES tab
- Switch to EMB_RES tab, the watch on the EMB_RES tab is frozen
- Clear all watches on all tabs
- Disable and enable monitor
- Switch to App tab, enable monitor and watch on FB's
- Switch to EMB_RES tab to see remnants from App tab
This is the App tab showing the watched. The linework is dashed but should be solid.
This is the EMB_RES tab showing remnants from App tab.
Latest .log file attached, looks like it might have a few more exception faults?
If I come across any other examples, I'll post them here.
|
|
|
Re: 4DIAC 1.13.0 IDE [message #1834798 is a reply to message #1834792] |
Wed, 18 November 2020 07:55 |
|
Wow. thanks for the detailed feedback. I must say the forum is not a very good place to handle so many different things in one place. But I'll try to answer a view things.
First of all thanks for the log files these help a lot to narrow down your issues.
Regarding the path issue. This is a general Windows problem which we can do very little about it.
One mapping issue has already been fixed and will be available in the upcoming 1.13.1 release. We still have to look into the issue that connections are not drawn correctly all the time. This seems to happen only on Windows machines.
The monitoring thingy will be a bigger thing to look into. There we have some major changes in the internal data structures that have to be rethought.
|
|
|
Powered by
FUDForum. Page generated in 0.05138 seconds