![]() |
Telelogic TAU (steve huntington) | ![]() |
Topic Title: File Format - Tau 2.7 to 3.0 Conversion Topic Summary: "Save All" not recognising format change? Created On: 26-Jan-2007 10:54 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Hello Greg / Ian, Yes you are right, this does work. The only tedious bit was that it prompts you separately to overwrite each file (our model has 98 files, so it gets boring), so a "Yes To All" option would be nice. But the main thing is that it works, so thanks for your help. Regards Graham | |
![]() |
|
I have a problem with conversion from V2.7 to V3.0 file formats. Tau changed the file format between V2.7 and V3.0, so the tool must convert the old format to the new format when loading old data initially.
This works OK, but it takes quite a long time - approximately 16 minutes on our model.
I could accept this if it happened once only, but unfortunately the "save all" function does not seem to work.
It seems that Tau will only save a file if you change something inside it. It does not seem to recognise that a format change also requires the file to be saved. So currently if I exit Tau it will take 16 minutes to reload my model, as the conversion process starts again from the beginning.
I can verify this by checking the timestamps on my files - even though Tau says a particular file has been converted from old to new format, the modification time doesn't change on the file.
Any tips would be welcome.
|
|
![]() |
|
![]() |
|
Graham
Tau has been deliberately designed to not rewrite the model files unless something in them has been changed by the user. This avoids unnecessary updates to files which haven't changed, but have only been opened in a newer version of Tau; there are many situations where a user would *not* want a file overwritten (and updated to the newer version of Tau) unless he had explicitly made a change to the model. To force Tau to save, you need to make an edit to a model element in each file which has no actual effect, such as changing a package name and then changing it back to the original value. You could do this manually, or you could contact your Telelogic account manager to get Professional Services help, for example to write a Tau addin to do the change/change back. Also, you could raise an Enhancement Request to support "to provide a way of forcing Tau to save converted files". HTH Ian ------------------------- ============= Ian Barnard Principal Consultant Telelogic UK, an IBM company |
|
![]() |
|
![]() |
|
Hello Ian,
Yes I can see why a user would not want a file to be re-written when nothing in it has changed. It especially causes problems when you have your model under version control. In fact I recall we have previously logged bug reports about it doing this very thing, so I'm glad that it's fixed.
Having said that, this really doesn't qualify as a case where "nothing has changed", because the entire structure of the file has been altered. It doesn't matter whether Tau did it or I did it, it has still changed - so Tau should at least give me the option of saving in the new format. Otherwise, it forces me to either make unnecessary trivial changes to the model, or wait an extra 15 minutes for my model to be converted at load time.
Most other software I can think of (Word, for example) prompts you to ask whether it should convert from the old to the new format when there has been a file format change.
I don't really fancy running round the model making unnecessary trivial changes, so what do you advise would be quicker - asking for an add-in or raising an enhancement request?
Thanks
Graham
Regards
Graham
|
|
![]() |
|
![]() |
|
Hi Graham,
We have had several requests over the years for this, and I agree with you. I've discussed this with the lab and hopefully we can sort something out in the next release. Another customer suggests this workaround (but I have not yet verified that it works): Go to the File View, select all of the files and press "Save" (not "Save All"). He checked the time stamps & file sizes and verified that they indeed got saved. Might be worth a try. Greg ------------------------- Greg Gorman Vice President, Product Management Modeling and Test Products Telelogic AB |
|
![]() |
|
![]() |
|
That certainly works for me on 3.0. Tau prompted me about conversion on a file which was from 2.7 but hadn't been modified, and the file time/size changed.
Thanks Ian ------------------------- ============= Ian Barnard Principal Consultant Telelogic UK, an IBM company |
|
![]() |
|
![]() |
|
Hello Greg / Ian,
Yes you are right, this does work. The only tedious bit was that it prompts you separately to overwrite each file (our model has 98 files, so it gets boring), so a "Yes To All" option would be nice.
But the main thing is that it works, so thanks for your help.
Regards
Graham
|
|
![]() |
Telelogic TAU
» TAU/Developer
»
File Format - Tau 2.7 to 3.0 Conversion
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.