Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File paths for keynote files #270

Open
jessbhamra opened this issue May 22, 2019 · 1 comment
Open

File paths for keynote files #270

jessbhamra opened this issue May 22, 2019 · 1 comment

Comments

@jessbhamra
Copy link

I know MC currently allows users to see file path locations for linked .rvt files, and the CTC Import & Link Manager shows locations of .dwg and image links and imports. It would be useful if MC could show the locations for keynote .txt files, wherever they were last located before they went missing. Also would be useful if a warning came up if a user is linking to a .txt file on their local machine or public parking. Related to issue #237 but for .txt links. Currently if Revit can't find the file, say it was on a user's local machine and they left the company for example, it just shows this:
image

@djsiroky
Copy link
Member

Going to ping @gschleusner on this because it seems related to the idea of external resource server mentioned in #237. I think the changes Konrad is making will provide many of the pieces needed to implement something like this and provide regular expressions as paths that would trigger a warning to the user.

3 possible ways of implementing this, increasing in dev time but also control would be:

  1. Try and retrieve the path when the situation in your image above occurs
  2. Warn/stop the user when attempting to use a keynote file in a forbidden location (defined by MC)
  3. Develop an external resource server that limits where external links (.txt, DWG, etc) can come from that is a reference to the project folder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants