Now you’ve found all the good stuff, why not create a short cut! You can now open any Windows folder and paste this address into the address bar: Short cut menu: Right-click in the command window, or (with no commands active and no objects selected) right-click in the drawing area, and choose ‘Options’.Ĭhoose the ‘Files’ Tab and click on the ‘Support File Search path’ Node to expand it.Ĭlick once on the first path you see to select it, click again to edit it – But don’t edit it! Just right click and choose copy. If you want to back up, repair or customise any of these files, you need to know where to find them right? How to find AutoCAD’s support paths. CUI file for your user Interface settings. To wrap everything up about this discussion before it derails completely: the Path WB has experienced a considerable amount of improvements in the 0.17-dev version so it would be best to wait for the new release instead of writing a 0.16 tutorial.AutoCAD references all kinds of files to help you create your drawings. Documentation is handled in the same way as Solidworks: copy+paste for things that haven't changed at all. Access is somewhat limited, though I have a Learning Advantage license that allows me to view the latest documentation for new releases. It's sorted per year/release version and some stuff is blatantly copied and pasted from previous versions because changes did not occur in some areas. The idea is good, I suggest looking at how other CAD programs and companies manage their documentation and see if we can adopt any useful ideas from them. This big of a change should definitely be tested, so let's postpone further discussion until I get a working testbed set up, eh? Then I'll create a new thread for it. The "dev" namespace at that point will be mostly empty for a long time.Īnyway, we have dragged this thread quite off topic for a while. ![]() Changes to the "dev" namespace can be made up until 0.17 release, at which point it will be cleared out into "stable" which can continue to have known-good pages added to it. Right now, if this feature were set up, current maintainers of pages could start making changes they may have already wanted to, and which may already exist in sandbox pages, which are themselves a namespace namespaces are already in use informally. I don't think it's much more work beyond the long-term maintenance that would otherwise be done with documentation. Yeah, before implementing something this big I'd definitely like to test it in my staging environment and see how it impacts everything, including translations. Seems sensible, but a lot of work, and not many people maintain the wiki's content. Kkremitzki wrote:That's sort of a long view, but in general, I think "dev" and "stable" should be the short-term response plan around the 0.17 release fracas. That's sort of a long view, but in general, I think "dev" and "stable" should be the short-term response plan around the 0.17 release fracas. That way it is clear that the content of a wiki page may work, but is not guaranteed to do so. If, instead, that version will no longer be supported, the pages could be dumped into an "unsupported" namespace. If that version then is no longer the stable major version but is still supported, then those pages can be moved into a numbered version like 0.17. Then, when 0.17 releases, we can do a batch move of all dev-namespace pages into a new "stable" namespace. ![]() My suggestion: rather than use a 0.17 namespace, we future-proof it by calling it "dev". ![]() That will allow pages to be easily cloned into the new namespace, although really old/big ones may need to be copy+pasted manually. Right, once the custom namespace is created, pages which *could* have 0.17-specific updates will now have a place to live. How does the user know which one to look for? Do we clone all the pages? So a 0.17 page would be 0.17:Path_Workbench ? More and more new users coming here and already on 0.17. The 0.16 vs 0.17 wiki issues are going to start popping up more and more.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |