Always modified with new version?

sohcd16y8 · Post by **sohcd16y8** » Fri Dec 25, 2009 10:17 pm

With the new version release, every time I open up a cal it says modified, even if I save it, then reopen it immediately. Is anyone else having this issue?

civic4g · Post by **civic4g** » Sat Dec 26, 2009 10:22 am

same here

Post by **calvin** » Sat Dec 26, 2009 11:41 pm

just updating cal rom version num

sohcd16y8 · Post by **sohcd16y8** » Sun Dec 27, 2009 3:08 pm

calvin wrote:just updating cal rom version num

It has to re-update it every time? It never did this with any other version update.

non-vtec · Post by **non-vtec** » Sun Dec 27, 2009 4:24 pm

same here.....ectune opens up last rom as \"modified\" every time. even after it has been saved.

non-vtec · Post by **non-vtec** » Mon Jan 25, 2010 8:16 pm

still does it even with the newest version...

relic1 · Post by **relic1** » Tue Jan 26, 2010 1:24 am

It shouldn't need to update it unless it sees a previous version in the cal... but the need for that info to be current is there. Just in case there is a major update to the program, or an incompatibility between versions type of issue. sort of like finding an old dos program and trying to run it on a windows7 machine. the newer software has to know that this is not a newer type of file so it can open it properly or not open it at all. Version encryption is the easiest way to do this. looking at this another way... it's also a hint that there are plans to make an update that will make this compatibility an issue. (there's been other \"hints\" as well)

sohcd16y8 · Post by **sohcd16y8** » Tue Jan 26, 2010 12:55 pm

relic1 wrote:It shouldn't need to update it unless it sees a previous version in the cal... but the need for that info to be current is there. Just in case there is a major update to the program, or an incompatibility between versions type of issue. sort of like finding an old dos program and trying to run it on a windows7 machine. the newer software has to know that this is not a newer type of file so it can open it properly or not open it at all. Version encryption is the easiest way to do this. looking at this another way... it's also a hint that there are plans to make an update that will make this compatibility an issue. (there's been other "hints" as well)

The issue is not understanding what the modified sign does, but why it is still popping up everytime you open up a cal. It doesn't mater if you save it, start new, etc it still says modified. One of the reasons I loved the modified sign being there was so that I was aware if any changes had been made to the cal whether intentional or by bumping a key, now it is just always showing modified.

relic1 · Post by **relic1** » Tue Jan 26, 2010 4:51 pm

calvin wrote:just updating cal rom version num

based on this, opening a cal automatically writes over the version tracking location. So the cal has changed. logical - yes able to be bypassed with a simple if statement (if the version is the current one, leave it alone) to prevent annoyance - yes adding this to his next update - only calvin knows

sohcd16y8 · Post by **sohcd16y8** » Wed Jan 27, 2010 12:03 am

relic1 wrote:
calvin wrote:just updating cal rom version num
based on this, opening a cal automatically writes over the version tracking location. So the cal has changed. logical - yes able to be bypassed with a simple if statement (if the version is the current one, leave it alone) to prevent annoyance - yes adding this to his next update - only calvin knows

Im with you there, the point is that it never used to do this, period. Only since the last set of updates has it acted this way, as if the "if" statement was removed.