Automatic read only?

[bradleydof]

I doubt that there is a way to make this less annoying, however I cannot find one instance of someone asking this so I thought I would take a shot in the dark.

On the personal license the program will change the read-only flag to editable after a save. Then I have to manually change it back, which is annoying because all the refreshes the side bar does at that point make clicking the menu to make it read-only again difficult to do for a few seconds. I will end up clicking it 3 or 4 times. If I just leave everything editable it complains about this 10 file (flag?) limit. I would love to find a way to automatically set the read-only flag after a save so I don't have to keep doing that manually anymore and everything can just be happy being read-only. What does that mean anyways? It doesn't seem to affect anything except the 10 file (or flag) limit. I can only save one file at a time anyways. Since it makes the files editable on save, I figure there has to be a way to make them read-only after said save. Then I think this might just be some weird way of making people want to pay to remove the restriction. Then I think, no. No company can be so petty as to make their software actually annoying to use just to extort money. So I am left with more questions than answers. I shall turn to the wisdom of the forums for a second time.

Thanks guys, I appreciate each and every one of you!

[lance.carocci]

---

@bradleydof wrote:

What does that mean anyways? It doesn't seem to affect anything except the 10 file (or flag) limit.

---

The Read Only state is intended to limit the number of files in use concurrently for Free licenses to a quantity that is reasonable for hobbyists and casual use, but inconvenient for an enterprise concerned with mission-critical productivity.

Rather than limit Free users to literally 10 files now and forever, Read Only allows users to still upload unlimited files to their Hub, but also demote files so as not to count towards the 10 file limit. You are free to change this flag often, but it is intended to be more for archival purposes, a state set once you are done working with that file, but without forcing you to delete it entirely just to make room for new files.

[bradleydof]

Ok, that makes sense. What I don't get is why it seems to not affect anything. Read only files can be open, edited and saved with only having to reset the flag after saving. I will commonly be working on several files at once with all of them read only. It's not till I save that it goes on the list. Then within seconds I put it back so I don't forget to. Makes me want to write a script that saves it and makes it read only at the push of a button. But I am lazy and that would be too much work. So I turned here. If that's the way it is then I'll just deal, as I have been. It's only a strange annoyance and not a deal breaker. I was just hoping there was a work around to make the file permanently read only or such. Still a great piece of software IMO.

[lance.carocci]

It's really only an issue if you are trying to actively edit/maintain 11+ files at the same time, which is uncommon for casual use. It wasn't the intention for Read Only to be the default state, rather it was a compromise over setting a hard 10-file limit (which could easily be taken up by a single assembly, its components, and drawing/schematics).

[bradleydof]

Interesting. I must be doing something wrong then. My last project was 30+ files. Each piece was it's own file. In fact, a decent portion of my projects are 10+ files. That makes me feel like I am organizing my components wrong. Is there a way to have all 37 pieces in one file? That's apparently why I'm so frustrated with this limit. Just yesterday I was editing 12 or 13 different pieces of one unit(case, cover, screws, additional features too difficult to print in place, etc) and getting them ready to print.

Thank you for taking the time to explain this. However, now I am baffled as to how one keeps within the 10 file limit on a project. With as many files as I make for ine project no wonder I find it frustrating. It is too bad the best compromise I have found makes saving a file a 5 to 8 click process (depending on how many clicks it takes to open the read only/editable menu). I understand that the default is supposed to be editable, however me defaulting to read only is the best compromise to this issue for me.

Any tips on organising different pieces to one part and keeping the file count down would certainly be welcome with a smile and open arms.

Thank you  I truly appreciate the time you have taken to answer my questions and deal with my relatively feeble attempt at remaining level headed.

[karina.harper]

@bradleydof 

Do you use a mix of internal and external components? Is there a reason you are mainly using external components? 

If you insert components, you can break the link and make it an internal only part, but you won't be able to get updates when you change the source. That would help you reduce the number of files you have active.

Cheers,

Karina

[bradleydof]

I knew I was missing something. I have some research to do because not only do I not know what internal and external parts are, but inserting components is something I know nothing about either. Then you mentioned breaking the link. Another thing I know not. Thank you for giving me some things to figure out to make my work flow more normal and efficient.

[karina.harper]

No problem @bradleydof - looking into internal vs. external components should help you. If you are trying to reduce the number of files you have in use, using mostly internal components will probably be the way to go 🙂 

Karina

[bradleydof]

Wow. The top down method seems powerful!

I was using it as a bottom up assembly. This completely changes the way I use fusion. Thank you very much for pointing that out! I knew I was doing something different. This now makes much more sense. I can't thank you enough!

Be well and be blessed!