Hello Steve
You have a information for a new update ,fix open flowcodev4 without a long waiting time?
Close all tabs are very "Maus-click intensive" for a big code with many macros..........
Regards Wolfgang
new Update
Moderator: Benj
-
saschech@gmx.de
- Posts: 714
- Joined: Wed Jan 31, 2007 12:41 pm
- Has thanked: 1 time
- Been thanked: 26 times
-
Steve
- Matrix Staff
- Posts: 3434
- Joined: Tue Jan 03, 2006 3:59 pm
- Has thanked: 114 times
- Been thanked: 422 times
Re: new Update
Hello Wolfgang,
A fix was implemented in the code in early May and so any Flowcode releases after this date will contain the fix. This is currently only the ARM version of the product.
It does take quite a considerable amount of effort to release a new version of Flowcode and try to minimise the number of releases throughout the year. I don't know when we are likely to release a new version of the PICmicro and AVR products, but there will probably be one in August/September.
A fix was implemented in the code in early May and so any Flowcode releases after this date will contain the fix. This is currently only the ARM version of the product.
It does take quite a considerable amount of effort to release a new version of Flowcode and try to minimise the number of releases throughout the year. I don't know when we are likely to release a new version of the PICmicro and AVR products, but there will probably be one in August/September.
-
medelec35
- Matrix Staff
- Posts: 9521
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
Re: new Update
Out of curiosity, would it be possible to place updated files e.g. .fcd, in a fcd zip file & .ocx in components a zip file etc in a updates thread.
Then we can extract into the Flowcode directory direct. That way we could update Flowcode, without waiting for more complex updating patch files to be developed. Then when an issue is fond, the zip file can be updated instantly.
I can see both side of the coin. It is great for us to have latest working files, but you don’t want to release too many patch updates.
Then we can extract into the Flowcode directory direct. That way we could update Flowcode, without waiting for more complex updating patch files to be developed. Then when an issue is fond, the zip file can be updated instantly.
I can see both side of the coin. It is great for us to have latest working files, but you don’t want to release too many patch updates.
Martin
-
Steve
- Matrix Staff
- Posts: 3434
- Joined: Tue Jan 03, 2006 3:59 pm
- Has thanked: 114 times
- Been thanked: 422 times
Re: new Update
It is usually fine for text files like the FCDs and changes to the underlying C code files, and we do issue these as and when they are made available.
But when "executable" files change (e.g. the main exe, the ocx files for components), the installer on the PC sometimes gets confused and tries to reinstate things the way they were before. It also means that some files you have will be updated and others will not - and these combinations are not necessarily tested together and have the potential to cause more support issues then they fix.
I know it must be deeply frustrating to know that the fixes to have been done, but are not actually available to download.
But when "executable" files change (e.g. the main exe, the ocx files for components), the installer on the PC sometimes gets confused and tries to reinstate things the way they were before. It also means that some files you have will be updated and others will not - and these combinations are not necessarily tested together and have the potential to cause more support issues then they fix.
I know it must be deeply frustrating to know that the fixes to have been done, but are not actually available to download.