Is there a release note for the 6.10 version?
What has changed?
Whats new in 6.10?
Moderator: Benj
-
medelec35
- Matrix Staff
- Posts: 9520
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
- Contact:
-
MJU
- Posts: 502
- Joined: Wed Nov 07, 2007 6:51 pm
- Location: Antwerp Belgium
- Has thanked: 121 times
- Been thanked: 108 times
- Contact:
-
medelec35
- Matrix Staff
- Posts: 9520
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
- Contact:
Re: Whats new in 6.10?
Not sure if you mean it should but does not, or you just agree with me and you found it ok?MJU wrote:Yes it should
Martin
-
MJU
- Posts: 502
- Joined: Wed Nov 07, 2007 6:51 pm
- Location: Antwerp Belgium
- Has thanked: 121 times
- Been thanked: 108 times
- Contact:
Re: Whats new in 6.10?
Isn't it common practice to publish a release note when a patch is send out to the world?medelec35 wrote:Not sure if you mean it should but does not, or you just agree with me and you found it ok?MJU wrote:Yes it should
I didn't install the patch (my version was 6.09), before I knew what had changed.
But after reading the post about where the changes are stowed away I installed the 6.10 patch.
In my logs folder there are a few change notes, but they stop after 6.03 (FlowcodeV6_Patchset6.0.3.txt).
There is a file "changes.txt" but this only holds changes from beta patches Matrix asked me to try.
So my question remains: what has changed with 6.10?
Re: Whats new in 6.10?
give you full coming right ..I'm talking the whole time already ...MJU wrote:...
Isn't it common practice to publish a release note when a patch is send out to the world?
I didn't install the patch (my version was 6.09), before I knew what had changed.
But after reading the post about where the changes are stowed away I installed the 6.10 patch.
...
It would be better to find out before the installation what has changed.
whether it makes makes the patch or the release or install the candidates should each user can decide before installation.
It would also be nice if a specific routine would return.
once new patches are announced then again not.
I find it sorry about bug messages to know that there is a new patch again.
but as this is now time unfortunately ...
rudi
....
my 5 cents ...for yourself:
no solution but a consolation:
unzip the install archive
search for the string
"Changes in this version"
in each file ...
then you know at least which file will be the log file ..
for v10 ..: read in the file fle_07262
zitat:
Changes in this version: alpha_70_140709
* Components *
- Feature additions -
Added new 4 x 20 character OLED type LCD component
- Bug fixes -
fixed lockup in TCPConnect due to goto connection reversed
return value was missing for sim version of TCPConnect macro
return value was missing for sim version of TCPConnect macro
target downloadable code did not work, now fixed
USB Serial SendString expected null terminator
* CAL changes *
- Bug fixes -
AVR Internal CAN seems to have some issues sending and receiving at the same time, current file does it's best to get this to work seamlessly
* FCD changes *
- Bug fixes -
PIC 16-BIT IOC Mapped Interrupt was broken, applied fix to all FCDs
Mod for some 18F devices with missing TRISE register seems to have a workaround already in place via BoostC
* Compiler changes *
* Flowcode executable *
- Feature additions -
add school edition splash screen
Load microcontrollers from restricted list, if present in licence
- Bug fixes -
fix splash screen timeout