Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
In one of our recent meetings with the customer advisory boards, @Anonymous suggest we try and engage the community earlier on with things we are working on. The idea station was suggested as a good place to do that.
Below is a concept to add searching to the post dialog. What are your thoughts?
Who is this "gearsoup" you speak of?! Old name that I retired when my business actually took off and settled on LibertyMachine
But yes, I feel strongly about engaging the skilled and dedicated community in ideas and discussions before dedicating a large amount of assets to it. Cuz, once something is started on in earnest, it greatly reduces the chance of any significant change being effected.
I like it. The Post Library is getting quite large (I wanted to say "bloated", but I feel that's a negative connotation). Will this eventually wind up in Fusion?
Yes, the library is pretty big. But we should make the install smaller.
You want people to go and download the latest post and not the one that was delivered with that build of the software.
I mean official builds can take months, so people will definitely take an old post in such a case.
The haas mill-turn posts have been updated about every week the last couple of months.
So if you ask me fewer posts with the software, more online and good explanation on how you place the posts you use in a folder and go to that folder in the post dialog.
This also comes with the advantage that posts won't be overwritten when a new build is installed. We have seen this cause trouble for a lot of users.
@Laurens-3DTechDraw I totally agree. It boggles my mind that so many people run the stock post from the generic location. Running the generic isn't so much the problem, it's the location they run it from. Every update brings a new batch of posts. So what worked yesterday "might" cause an issue today. That's why I try to tell people to "make the post their own". Save it on a personal folder or the cloud
@Laurens-3DTechDraw I run my posts from a separate directory I created. I do this so when I update the code I don't lose my posts. In my opinion the added search capability will add value to the new user more than an more experienced user.
Live-searching the current posts on the cam.autodesk.com/posts library would be pretty awesome, and I agree that it should be put into a local directory. I would stress that this library needs to be something simple to access and easy to find (even with an 'open post location' button in the interface somewhere perhaps). Also it needs to be able to be modified by the user. For instance, I use a Google drive folder for my posts at home which lets me edit them anywhere and not worry about updating manually.
Otherwise I agree with the newest iteration. Building the search into the UI makes it much simpler than pointing someone at the website and then having them download the newest one, add it to Cloud or Local posts, etc.
That with the search option I like more. And I agree that for Fusion this would be a great way to solve the post folder location madness.
Even though it doesn't help for users that need edits to their posts, someone on the forum helps them, how do they import them.
Effectively what I'm saying that the post dialog screen needs a good UI overhaul for this to really work.
Because now it doesn't seem intuitive at all for a new user.
If others have good Idea's on a new UI design I would love to see those, because the extra options like this are usefull features just not near 50% of their potential of when the UI was designed for this purpose and not having them just pushed in there.
(Example I don't think I've ever seen anyone use the setup button without being told by someone why it's there and what it does.)
@Laurens-3DTechDraw I am glad you bring this up. The post dialog does need a good overhaul and we should probably start a separate idea around that (if there isn't one already)
Internally, we have talked about the overhaul driving something we have referred to as an NC node that would add a number of functional improvements.
NC code would be produced when toolpaths are calculated - it could then be seen in the UI with the simulation
It would provide a place to visualize and see the effect of ordering on a posted code
I agree with @Laurens-3DTechDraw. I don't see all that much benifit to anyone more that new users if it is searching the install location. Now connecting it to the post library and allowing you do download the latest version would be nice. But even in that situation I would only be downloading it to compare to my modified post and incorporate any new updates.
I like the idea of seeing the posted code in the cam work space. However it would need to be clear that the code seen during simulation is not driving the simulation.
Actually, I think that is a different thing. The post dialog window should disappear when you select the post/machine before hand. Which is what you need for the NC Node. The great thing about that system is that everything would be stored with the setup. So next time there is no guessing to what maximum spindle speed you set when posting etc.
And since we are not months, but years from something like that I would say give the current Post dialog a much-needed update.
About simulation and code, in that case, I think indeed that showing the code move along with the simulation means you actually need an NC-code to simulation engine. And not go taking a wild guess on code vs movements. The problem there is that the post processors would be limited to a certain amount that are supported. Or you would have to change the post built-up completely and not allow the full javascript access, but just have a fill-in screen with what code is spindle clockwise, what code is TCP on, etc. And since I don't think we want either of those problems, I'm not sure if this is ever going to work.
I don't want to seem like I'm hijacking this thread, but while the development team is hammering on the post UI section how about implementing this idea at the same time.
