|
Re: Function TIME() [message #1740716 is a reply to message #1740693] |
Wed, 17 August 2016 17:45 |
|
Hi,
No, unfortunately this will not work as expected. The first reason is that the time function only returns the time that has elapsed since FORTE was started. So you could use it to measure the time on the start and at at the next event and calculate the difference. However you would need a dedicated event.
The best option to do this is to use the ATimeOut adapter. You can find examples how it is used in the traffic light example. However this requires the chnage the FBs interface. This is no problem you can update an FB interface in your application by inoking the context menu update FB.
I hope this helps.
Alois
|
|
|
|
Re: Function TIME() [message #1740955 is a reply to message #1740757] |
Sun, 21 August 2016 11:46 |
|
Hi,
no it is definitely not your mistake. The problem is that when you press "Update FB Type" 4diac tries to match the existing connections with the new FB type's interface. The only thing we can currently do is that we are keeping the connections to the interface elements with the same name. If you are changing a name of a FB interface element (e.g., REQ to REQ_RD) then we can not match this anymore automatically and currently delete the connection. Therefore if you only add interface elements or delete some the network will still be correct after the update.
We have some ideas to improve the situation in the future by showing you a dialog with the connections that would be lost and give you choices to which ports you may want to connect them. Any ideas how to present this and what would be needed are highly appreciated.
BR,
Alois
|
|
|
|
Re: Function TIME() [message #1741569 is a reply to message #1741449] |
Thu, 25 August 2016 21:16 |
|
Hi,
thanks for pointing this out. I think you found a bug in 4diac-ide. I hope you have saved your project so you can back up.
Can you please tell me which 4diac version you are using. From the error message dialog that is shown in the figure it looks like it is not 1.8.0.
BR,
Alois
|
|
|
|
Re: Function TIME() [message #1741635 is a reply to message #1741602] |
Fri, 26 August 2016 13:31 |
|
Hi,
The latest version is 1.8.0. We did lots of fixes between 1.8M1 and 1.8.0 but I don't know if your issue has been fixed. I also don't know how much effort it would be. Would you be so kind and give 1.8.0 a try?
Instead of making a new FB you can alos change the old type. But then instead of invoking the update FB perform the manual changes as you are suggesting.
|
|
|
|
Re: Function TIME() [message #1741789 is a reply to message #1741708] |
Mon, 29 August 2016 15:40 |
|
Hi,
thanks for the info. Instead of the error message there should have been a pop-up on the bottom left with automatic error reporting. Did you see this?
Would you be so kind and report a bug in our bugzilla so that we can keep track of this issue.
BR,
Alois
|
|
|
|
Re: Function TIME() [message #1741871 is a reply to message #1741861] |
Tue, 30 August 2016 10:34 |
|
Oh ok. We integrated an automated error reporting infrastructure which can report such issues for you. Normally when I tested it it showed a small pop-up on the bottom left. On the first error the pop-up asks if it automatic error reporting should be activated. And on any further error it asks if it should send it. This should make it very convenient for you to report issues. And it makes it very convenient for us as we get some stack traces and furhter information on the state of 4diac-ide. Helping us to track the error down.
|
|
|
|
Re: Function TIME() [message #1779409 is a reply to message #1779301] |
Sat, 06 January 2018 18:07 |
|
Dear Daniel,
thanks for bringing this up again. I think we somehow lost track on this during the work in 4diac-ide 1.9.0. As we are in the final phase of the 1.9.0 release could you be so kind and give the 1.9.0.M2 a try? We did an enormous amount of changes under the hood and if the issue is still here i would like to fix it in the 1.9.x code.
thx in advance,
Alois
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05331 seconds