Announcements
Welcome to the Revit Ideas Board! Before posting, please read the helpful tips here. Thank you for your Ideas!
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

BasicFileInfo.IsCentral is true for copies of central files

BasicFileInfo.IsCentral is true for copies of central files

When I use BasicFIleInfo.Extract() on a recent copy of a central file it returns a BasicFileInfo instances where IsCentral is true and IsLocal is false. However, a copy of a central file should be considered a local file. It seems that IsCentral and IsLocal do not change until the local file has been opened and saved by a user. 

 

Shouldn't any workshared file at a location other than CentralPath be considered a local file?

 

Here's an example output from BasicFile info. The target file is "Revit 2017 Sample - Copy.rvt", which is associated with the central model "Revit 2017 Sample.rvt". Yet the BasicFile info has IsLocal = false, and IsCentral = true.

 

 

basicfileinfo.png

5 Comments
lionel.kai
Advisor

The existing behavior you're describing actually makes sense to me, and is probably just exposing the Revit internals that are used to determine if Revit should present the "this central file has been moved or copied" dialog to the user.

 

Maybe what you should be requesting is a "IsMovedCentral" property (which just would be an AND of: IsCentral and CentralPath = current path)?

eric.anastas
Contributor

A moved or renamed central file is essentially a local file. "IsMovedCentral" implies that the file is still a central file. Yet unless it was renamed/moved back there would be no way to sync back to it as a "central" file. So I don't see how this could be considered a central file.

 

"IsNewLocal" might be a better name? Meaning the file is a newly created local file. But as you said checking the (IsCentral & CentralPath == currentPath) is not that difficult.

lionel.kai
Advisor

Your name is definitely better than mine, but now I'm thinking that "IsACentralFileThatIsNotWhereItShouldBeAndTheUserHasNotBeenNotifiedYetSoWeAreNotSureIfItIsReallyMeantToBeALocalFileOrIfSomeoneAccidentallyMovedRenamedOrCopiedIt" would be a much more accurate and clear name of the calculated value. 🙂

sasha.crotty
Community Manager
Thanks for taking the time to submit your idea. Unfortunately, this idea did not get the support of the community over the last 6 months and as such we will not be pursuing it at this time. Please feel free to rework (titles and clear descriptions are really important) and resubmit this one down the road.
sasha.crotty
Community Manager
Status changed to: Archived
 

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea  

Autodesk Design & Make Report


Autodesk Design & Make Report