AU Class
AU Class
class - AU

AutoCAD Tool Palettes Management Lab (Planning and Preparation, Not Perspiration) (REPEAT)

共享此课程

说明

CAD standards are a bone of contention for every CAD manager. For me, CAD standards are all about a single thing-productivity. It's all about decision making. I don't want you spending time deciding what font to use or what lineweight to draw with. Those tasks don't increase the project's value. I want you to be able to focus on creating drawings that sell ideas to a client or help make manufacturing quicker and easier. You shouldn't need to worry about CAD standards. In this lab, we'll go through the exact steps that I use to create a comprehensive set of tool palettes that deploy our company CAD standards. I'll show you how to deploy your tool palettes on the network, and how to update them from a central file. We'll push as hard as we can into deploying scripts and macros from tool palettes, and cover some of the tips and hacks of tool palettes that you won't find in the help file.

主要学习内容

  • Learn how to create a completely fresh tool palette in a network location
  • Learn how to create, edit, and save tools onto your networked palettes
  • Learn how to boost productivity with scripts and macros hosted on your palettes
  • Learn how to hack your tool palettes without opening AutoCAD

讲师

  • Paul Munford 的头像
    Paul Munford
    Paul Munford is a CAD geek, Customer Adoption Specialist for Informed Design and Autodesk Expert Elite Alumni. Based in the UK, Paul's background in manufacturing items for the construction industry gives him a foot in digital prototyping and a foot in Building Information Modeling (BIM). Paul was a speaker at Autodesk University for the first time in 2012, and he says it's the most fun anyone can have with 250 other people in the room.
Video Player is loading.
Current Time 0:00
Duration 1:26:25
Loaded: 0.19%
Stream Type LIVE
Remaining Time 1:26:25
 
1x
  • Chapters
  • descriptions off, selected
  • en (Main), selected
Transcript

PAUL MUNFORD: Well, good morning, everybody. Welcome to AU. How many people are at AU for the first time? Wow, quite a few. How many people have never been to a lab AU. Can I let you a secret? This is my first lab AU. Not the first one I've been in, the first one I've presented, so be gentle with me, OK? So welcome along to this class. This is AutoCAD Tool Palettes class. So I'll just show you this slide to begin with, just to make sure everybody's in the right room, OK?

So today we're going to be doing a step by step introduction to maintaining your CAD standards to using tool palettes. I've tried to make this, rather than make it too generic and not have it work for everybody, I've tried to make it very specific. So it's a very specific step by step workflow that we'll go through to show you how to deploy your tool palettes across your server. So I'm kind of hoping that you'll get to take this away and have a go at it and then apply it in your company.

So if you are using an AutoCAD vertical, like simple 3D architectural desktop, there might be something in there for you to use. So in this class, I'll help you better complete completely fresh tool palettes in a network location, create, edit, and save tools in the network pallets, and boost your productivity and share to add scripts and macros to your palettes. Hack your tool palettes without opening AutoCAD. Well, there's something about that in the handout.

Unfortunately we couldn't do that today, because it requires an XML editor, and I couldn't get one installed on the machines for you, so that bit you'll have to take a look at. So I'll just introduce myself. My name is Paul Munford. I'm an application engineer for an Autodesk reseller in the UK called Graitec. So my job is to help our customers get the best out of their investment in their Autodesk software. But until two years ago, I was a CAD manager at a company making bespoke high quality furniture, and tool palettes were right at the heart of the way I put castanets to get to help our people work more efficiently.

Today our lab assistant's up the back there. So if you turn around and give him a wave-- give him a wave, everybody. So these guys are all CAD managers in their own right, and they're people that I am fans of. So I'm really so pleased to have them here. And Autodesk university is all about networking. So whatever you do, whatever problems you're having at work, there will be somebody in this room who's had the same issue. So do speak to people while you're here.

Speak to people in the line up for the gent's. Speak to people at breakfast. Speak to people when you sat next to them in the class. Say hi. Swap business cards. The contacts you make at Autodesk University will be as valuable as the information you take away. And there's four great contacts in the back there, so if you want to introduce yourself, anytime.

The lab assistants there to help you. So if something unexpected happens, if you're getting a little bit behind with the exercises, if you have a question, just put your hand up and one of these guys will run in and help you out. So the way this is going to work out today, I've got a short presentation to give you first just to set the scene for what we're going to do today and why we're going to do it. Then I've got a series of exercises for you.

There's an exercise handout PDF, which we open up on the machine. So it should be ready and waiting for you. Did everybody get the message that there's no printed handouts at Autodesk University? OK so you've either got the one on the machine, or if you've got it downloaded onto your handheld device you might better follow along with that. I'm going to demonstrate each exercise before we do it, and you'll have a couple of minutes to do the exercise.

Please watch the demonstration all the way through, right? Don't try and follow what I'm doing on the screen at the same time, because, as you're looking up and down, you might see some clicks. Just watch the presentation, and then you've got the handout. You can follow it through. I may have to sort of stop at each point and say we've run out of time on the exercise. So if you haven't finished, I'm sorry, but watch the next presentation. We'll move on to the next one. But the guys, again, in the back there can help you out if you get too far behind.

So let's just begin with the presentation. So tool palettes to me are about CAD standards. And the whole idea about CAD standards, for me, it's not about me being so OCD or being worried about the way our drawings look. In fact, I'm not that worried. So one of the guys at my office once said this to me, "I don't want to be able to tell who did this drawing until I look in the Title Block." And I thought, well why? Because back when we used to do drawings by hand, you could tell who did the drawing. You could tell from the way we draw lines, let alone the way we did our lettering.

So is that really of a benefit? I thought, to me that's not really the benefit of CAD standards. The benefit of CAD standard is that we don't have to spend time thinking about line waits and line types and what func should we use. To me, that's not value out when we're drafting. When we're drafting, we're thinking about am I delivering to the customer? Am I delivering to the quality? Cover my internal costs. Am I delivering on quality? And am I delivering to my company? Am I thinking about the best design I can come up, the most efficient, one that's going to cost us less but still delivers to the company?

That's what I want my drafters thinking about. I don't want them thinking about line waits and line types, all that stuff. That should just be kind of set. So the reason why is something called decision fatigue. I don't know if you've come across the expression. It's this idea that more decisions you have to make in the day, the less quality. The quality of your decision goes down you start to kind of flag. But I've actually proved this with judges, doing court cases, that their decision making ability flags until they have lunch, and then they feel better and then it goes down again.

So I don't know, Steve Jobs always used to wear the same outfits and I heard Barack Obama would choose to eat the same meals. And it's not because they are not creative or not interested in that stuff. It's because they didn't want to make decisions about those things. Just forget about that stuff. I've got more important things to make decisions about. Yeah, so I don't want people making decisions about layouts and the way things look. I want them making decisions about the end product, not the drawing itself.

So I put an example here of something I wouldn't mind, right? So putting text in bold text, it kind of violates my CAD standard, but I don't mind. I appreciate this person was concerned about this note, right? So I think it's good they're concerned. I want them to make a small violation in the CAD standard. I'm not worried. That's not going to cause anybody any problems. It didn't take long to do. I would draw the line at this one.

You spent a long time messing up my CAD standard to produce something that looks worse. That's too far. So I don't want people doing this. I want all this to be set. I want the CAD to be so easy to use that they prefer to use the CAD standard than not. How do we use standards in AutoCAD? The hard way. All right. So firstly, we've got to decide what we'd like to draw. That's kind of a given. Then we refer to the CAD standard.

You all do this? You all go and get your CAD standard and you just have to look through it first before you start drawing? Yeah. And how many people have [INAUDIBLE] in your office who do that? I bet they all do it, yeah. Then, make sure we use the right template that's got our styles and layers set up in it. Then we select the layer we want to work on. Then we select the style we need to use. Then we navigate to the tool we need to use. Then we can start drawing.

Right, is it any wonder our users don't do this? Too many steps. They have no interest. That's why they draw everything on layer zero. "Whatever, I'll just start drawing." Yeah, so we don't want that. We don't want that. It's got to be easier than that. We've got to find a way of making this easy. Otherwise people won't use our standard. So our objective is compliance to the CAD standard.

We want people to be working efficiently and effectively. We don't want them thinking about the CAD standard. We just want them to use it. But we're busy, right? So how many people actually still have to do production work as well as managing CAD systems? Yeah? Quite a few of you. So when I was a CAD manager, I was 50% billable. So I had to bill at least 50% of my time to projects.

About 25% of time was non-bailable. That's meetings, holidays, you know, that kind of stuff. But we all know that project work takes up all available time. So I didn't bill 50%. I billed just about everything. I didn't have much time left for CAD standards. So whatever we do here had got to be easy to set up, because we don't have much time to do it. Right? So we've got to better set this up easily and quickly. It's got to be easy to deploy. We don't have a lot of time to be going around everybody's machine to set this up, so we've got to find a way of pushing out to people's machines so it can be done efficiently.

It's got to be easy to use. This is for our CAD users. It's got to be easy to use, otherwise I won't use it. Path of least resistance. If it's easier to use the standard than it is to do it the hard way, they will use the standard. But if you make it too hard, they won't do it. It's got to be easy to update. We're full of good ideas. We see stuff all the time and go "we could make this more efficient. We could save a couple of clicks. We could put a process together. We could improve, not just the standardization of our drawings, but the standardization of our method." So when we get a good idea, we want to better update the system quickly and easily. We don't want it to be a lot of hard work.

And easy to migrate. So year on year, when the new issue of AutoCAD comes out, we don't have to spend a long time testing up all our routines and programs to make sure they still function under the new system. So for me, that's why I chose tool palettes. I had tried lots of other different ways to implement stuff, and I just found tool palettes were just be easiest to set up and migrate and customize.

So we're not going to learn about today. We're not going to learn tool palette basics. So I hope you all used tool palettes a little bit before. This is about deploying tool palettes across networks. It's not about creating them. Anybody who's never used a tool palette. If you haven't used a tool palette, Matt Murphy's class is awesome. I highly recommend it. He's been giving this class for years, and a big reason is because he's very, very good. In fact, if you know tool palettes then show this to your users and get them using the tool palettes as well.

OK so what's difficult about tool palettes? Well the difficult thing about tool palettes is that tool palettes save when AutoCAD closes. So you create your tool palettes. You shut down AutoCAD. It writes out the changes. So if we just take our tool palette files and just put them on the network, what happens is-- there's my tool palettes. I've created them on the server ready to deploy. I start up AutoCAD, and AutoCAD pulls in a copy of those palette off the server. So now I've gotten in my old CAD system.

So I'm very happy with that. That's great. And it's a very small CAD department. It's just me and my colleague. But when my colleague comes to work, he opens up AutoCAD and he pulls a copy the tool palettes from the network too. So now we're working off the same set of tool pallets. This is good so far. But what happens is, I have a great idea and do some changes. And then I close AutoCAD and writes the changes back out to the server.

Awesome, this is all still good until my colleague shuts down his version of AutoCAD and writes out the old ones back off the top of my version. Well, now I'm sad. All my changes have gone. So we can't just put AutoCAD tool palettes on the server. We have to kind of work around that little bit, and that's really what this class is about is how do we put a set on the server that our users can use, but they can't mess them up.

So bit of preparation for you guys when you get back to the office. To do this effectively, you need to have firstly a graphical standard. So when I'm helping customers set this up now, I need to have a graphical standard to work with. What line weights do you want to use? Are you going to go with-- in my case, it's usually BS 8888, British standard for technical drawing. It could be PAS 1192 now, starting to be more BIM stuff. But you've got to have this graphical standard first. That's got to be somewhere. And then we also need to have, what I think of as, a data standard.

So which template files are we going to use? Where are we going to save our drawings? What about X-refs? How we can set those up? What about revisions? If I'm doing revisions to my AutoCAD drawing, do I need to archive a copy off or rename it? What's going to happen there? And then outputs. What are my outputs? Is it going to be paper? Unlike these days, people more like to be PDF, could be DWF, but I guess not. And what do I do about revising those?

So again, this is stuff that we need to have thought about before we can start. We can't automate something unless we know what we're automating, right? And also there's actually two hand outs for this class. There's the exercises we're gonna do today and there's the handout that I did to go with this is a presentation. I gave this presentation at Autodesk University a couple of years back. And I've given instructions in there on how you can open up AutoCAD tool palettes in XML editor, and then you can do some pretty cool stuff in there.

For example, if anybody's ever created a block insert block tool on the tool palette, and then you moved the original block and it's broken, well you can open up an XML editor and do a find replace on the block path and fix it. Yeah, so there's some extra bits in there you might find useful. For this lab, a couple of things we did for you before the class started. We've made sure that AutoCAD is set up to-- it's not been used before. So it should be a default install. We've also set the no logo startup switch, so you shouldn't have the splash screen start up. This is because we are going to shut down, open up AutoCAD c a few times in this class right, so we try to make it as quick as possible to open up for you.

And we opened up the dataset folder on your drive, so you should see that. And we opened up the excises, so you should have that. Good, so let's take a look at some of these exercises. So if you don't have the dataset folder open, that's where it's going to be. So there's a folder on your desktop called datasets. Within that, there's a folder called Paul Munford, and within that is the class ID. We're looking at the exercises PDF today, not the handout. That's just an extra bit of material for you if you'd like to have. You want the exercise handout open.

So there's some additional material there. And I have recorded these exercises as Screencasts. So if you want to again and review this in your own time later, you can watch these exercises back on the screencast.com site. And also I just found out this morning, I got this written down so excuse me I don't have a slide for this one, all the data sets are available at self-paced labs. So in lead 03101 on this level, there's a lab where you can go and sit down at a machine at any time in the day. It's up to you, it's self-paced. You don't have to break in or anything. And all the datasets are preloaded there for you.

So again, if you want to practice this while you're AU this week, or if you want to direct a colleague to do it, come look at this with me. You better get the excises there. So that's 3101, self-paced labs. Good. So we're going to start by just creating some folders, so I'm going to jump into the demo here. So I'll just minimize everything. If you just like to open up what will effectively be the C drive on your machine. So generally speaking, when we start this, I recommend creating a map drive on your server for your CAD stuff, and I put some instructions in the front of the handout on how to do that.

Unfortunately we couldn't do it here because of the way the machines are set up. So if you could just open up your C drive and create a new folder in your C drive. So we'll create a new folder and we'll just call it palettes. And that's where we're going to save everything for this class.

So then, if you could go to your data set-- and me just find mine. We want to copy the four folders there, build, deploy, resources, and support. We'll copy those four folders into that palettes location, into that location on your C drive. So the dataset file, is it open on your see machine? When are you guys-- [INAUDIBLE].

So you'll find the two folders they're building deploy currently empty. There's nothing in them yet. That's the ones we're going to fill up with tool palettes. Resources and support, I put some stuff in there for us that we can use as we go through. The step by step instructions are in the handout. So you might have guessed, I'm from the UK. So if anybody is struggling with my accent, or if I'm going to quickly, it's all in there.

OK so I'll go on to the next slide. Also, I've put the page that the exercise is on up in the top right of the slide there. So that should help you find that as well. OK so we're going to do a few more steps in this one. So we're gonna start by creating an admin profile. So who's worked with profiles in AutoCAD before? Quite a few. That's good, right?

So this is how we are gonna target where AutoCAD is going to work. So this is our profile, as the CAD admin. So this is going to be our set of tool palettes that we're going to be able to build. They are going to be editable. These are ones that we update. And then later on, we'll create a different profile for users now pointing towards a different set that's locked. So we're going to create the admin profile. We're going to set our support palettes up, add a default template. I'll talk about trusted locations. And we're going to tell AutoCAD where we'd like to build these TOOL palettes, and then we'll create a couple of tools.

So maybe I'll just show you the first couple of steps to begin with, and then we can pick it up from there. So we can boot up AutoCAD. My AutoCAD is still booting. Hurry, hurry. Apologies for this, folks. There's nothing like AutoCAD opening up perfectly the first time you try and then not when you really need it.

I need help from one of the lab assistants.

OK, thank you for your patience, everybody. I've got a different machine running with AutoCAD on it. So the first thing we're going to do is we're going to start by opening up the options. So the easiest way to do this is just type "options" at a command line. So if you've got a preference for the way you like to open up the options, go ahead, but I'm just going to type in "options" there. And the first thing I'm going to do is create our admin profile. So, again, you just want to maybe just watch these, and you can follow along using the handout at the moment.

So I'm going to switch over here to the other end, to my profiles tab. And in my profiles tab I'm going to choose "at list" and I'm going to create a profile here called admin. So when you get back to the office, you can call it whenever you like. But for today, call it admin. Notice that when I click "apply" and close the top of the screen there, we can see it says unnamed profile still. So although I've created an admin profile, it's not yet current. So we do want to make sure that we select the admin profile and choose "set current." Now we'll see at the top of the dialog, now we see the admin is written there.

So now we know the admin profile is the current profile. Anything we do now is going to be saved against the admin profile. So keep with me. I'll do a couple of more steps. This is all written in the handout, so you should be able to follow along. So once I've got my profile created, I'm going to switch to the files tab, and I'm going to do a few changes in here. We're going to set a few support paths. So the first thing I want to change is in my support path. I want to add those two folders I created. My support folder, which has got things like templates, my CAD standard in, and my resources folder. The two folders where I keep resources, is where I keep scripts, and in macros, and all that kind of stuff.

So to add a path here to the support paths, I'll just click over here on the left "add," then it asks us where the path is. You can copy them paste the path in here, but I'm going to pick on "browse," and browse to this new folder, which I now have to create because I did that step on the other machine.

Why can't I create a new folder? Is anybody having this problem as well? I've created it, I just can't spell. All right, got there.

Yep, so back in AutoCAD I'm going to browse to my local drive, my C drive, find that palettes folder we created, and I'm going to add my resources folder. So I'll click on OK right here, and then I'll do exactly the same thing again. So add. This time I'm going to click "browse," browse back to my C drive, palettes folder, and this, I'm going to add my support folder in there. So maybe you guys want to get to that step. Create your admin profile. Make sure you set it current. Then come back to your support, and set up those two folders in support And while you're doing that, I'll just give one more tip. If you like, you can click on the move up, and you can move these extra folders you've added to your support paths to the top of the screen. And that just means that AutoCAD is going to search these locations first. So go ahead and do those steps, if you haven't done them already. And then I'll give you an extra couple of steps in a moment.

How are we doing? Everybody with me so far? Anybody not manage any of that? OK, so if I could have your attention again-- so working our way down these support paths, the next one I'm going to come to is the trusted locations. So who's used this trusted locations path before? Yeah? Small number of you. So this is relatively new. It's been added to AutoCAD in the last release or two, and it's been put there as an extra security measure.

So what they're saying is-- if you're running your own programs, your own scripts, list routines, VBA macros, whatever you've got-- it needs to be run from a trusted location, otherwise AutoCAD will pop up like a splash screen all the time saying, do you want to run this program or not. So we can add a trusted location in there. So I'm going to click Add and Browse again. We're going to browse back to the C drive palettes folder. And we want to add our support folder to the trusted locations. So the support folder's where we've got some macros, which we're going to run later.

So I click OK there. Click Continue. And that's added that on. So trusted locations are something we'll set up. Now the whole point of this set up is that, because we are using our tool palettes to drive standards. We don't need to have a template file that's got all the styles and standards in THEM because our tool palettes remember the standard. So when we use a tool palette tool, the standard is created. So we can use a template which is completely blank. And what's nice about that is we don't end up with a lot of extra crud in our drawings that we don't really want to be there, because we know that everybody should delete that stuff on the template, but they never do.

So let's start with a completely blank template. So for the template, I'm going to select say where it says default template for [INAUDIBLE]. So this is the default template. It's used whenever you click on the New button. And we're going to click on Browse there, and we get to add in from our C drive palettes folder from our resources folder. I put a copy in there of aCAD.iso, because I'm European so it's an ISO standard aCAD. aCAD.dwt. So if you could pick on open there, that just sets that as being the default template. So you can have your own default template. Set it in whatever units you like.

How are we doing? Everybody with me so far? OK so next up is the absolute key one. This is the one that we all came for. We're looking here at tool palette file location. So this is where AutoCAD, by default, is loading in tool palettes. These are the default tool palettes that come with AutoCAD, but we don't want to use the default ones. We want to use our own ones. And this is a tip I actually picked up in Matt Murphy's class.

What you can do here is we're just going to get rid of this location. We're going to put our own location in. And we don't to worry about the fact it's not pointing at any tool palette files right now. When we close down AutoCAD, it will create the tool palettes in that location, which is pretty cool. So get a brand new blank set of tool palettes that we can build.

So what I'm going to do is I'm just going to click Remove to remove the standard path, and I'm going to click and browse to C drive, palettes, build, right? So our build folder is where we're going to build our set of tool palettes. That's all working folder for us CAD Admins. We're going to add that as our tool palette file location. So while you're doing that step, you can go ahead and do that couple of steps, I'll just mention a little tip there. You can have multiple tool pilot locations. So you could keep the existing tool palettes, if you felt like it.

But AutoCAD will write its tool palettes to the first location in the list. Yeah? So different profiles, you can have them in different orders. You can have multiple sets of palettes. You could have a mechanical engineering set of palettes, a Civil engineering set of palettes, an architectural set of palettes, and have them all in that folder there, in that one location.

Let me just check over here. Yep, everybody with me? Good. So that's our support path set for the time being. So we can pick OK there. I'm just going to close the options down. And now let's create a tool palette. So I'm just going to open up the tool palette so I can see them. So I'll just type in "palettes." And that's going to open up out tool palettes right here. So maybe I'll just scrunch these down a little bit.

One tip with tool palettes, I don't know if you've noticed, but if you don't want them to dock, hold down the Control key and they won't dock to the sides there. OK so I'm going to rename this palette. I'm going to call this one "CAD standards." No, I'm sorry. I'm going to call this one "draw." That's what I decided to do. So once you created a pallet and renamed it, we'll put a tool on it. And then we're gonna close down AutoCAD, and we're going to see what happens when we write out these changes.

So to create a tool, if you could open up, from our resources folder from our support folder-- oh no, from our resources folder there should be a DWT file in here called global template. Every time I hit right click, it shuts. Right, so I'll just show you there. So if you could open up this file here, from your palettes folder resources, called global template. So I do start with a global template, and in my global template I've defined all my layers, and all my styles, and all my texts, and everything I need. We're just not going to use that as a template to start drawing, because we don't want to have all this stuff in our drawing.

So I'll open this up. And if you guys could zoom in. And from the ISO Standard line definitions over here, we're just going to create a tool. Who's never created a tool palettes tool before? Wow, it's like one of you-- yeah perfect, right. So you're up to speed with that. So yeah, we're just going to pick this layer call "visible." So I'm just going to select this line with a left click, and I'm going to right click and just drag it onto my palette.

So it's just a sample tool we're going to create, just so we can see what happens when we write these out. Let's rename this tool. So once you've created a tool, I'm going to right click and choose Properties. I'm just gonna name this "visible lines." Draws lines on the visible layer. So how many people take the time to put a little description of their tool when they create tool palette buttons? I think the chap down here needs some help.

So you've notice that, when you change the description, your description becomes a tool tip. So again, you can improve your standard, use of standards, by giving people tool tips. When they hover over the button, they see what that button does. The class is being recorded, so you better watch the class back next week. And all the handouts are uploaded to the web site. Yes you better download the handout and the data. Great. Everybody with me?

So when we're done, we want to close down AutoCAD. so I'm going to close the global template file. I don't have to save any changes, and then we'll close AutoCAD. And I'm expecting to see my tool palettes, so where are they? Oh yeah, hit C, palettes, build. Good. So what we should expect to see, in that location we set for our two pilot offering-- So we set on our C drive, we had a folder called palettes, and in there we had a folder called build. We should now see we've got a folder created called palettes. And this thing here call the ACTP catalog .ACT file. Does everybody see that OK?

Right, so I've put a description in that longer form handout with exactly what the catalog file is doing and some extra things you can do. You can open up this XML file, and you can take a look at what's going on inside it. But we're not going to do that exercise today, because we couldn't get an XML reader. But if you double click into the palettes folder, you should see another ATC file. This one will be called "draw," because that's what we named our palette.

And then I'll have a big long GUID, which is a Global Unique Identifier, after it, which we don't need to worry about. So if these steps happened, we're good. Is everybody okay with that? Anybody not see that happen? Fantastic. So we've written out the changes. Let's boot AutoCAD back up again, and we'll add some more stuff to the palettes.

Fantastic. Everybody with me? Yes, good. So we've learned that we can set the support paths up or we can write our own set of palettes to our own folder. So let's just create another couple of palettes here. So I'm just going to right-click over here. Where's my mouse gone? Right click anywhere on the palette and choose New Palette. So I'm going to create one here called CAD standards. I'll create another one here called library. Now the order these palettes will be seen in is set up in your profile. That's one of the reasons we're deploying it via profile.

So if you're very keen that these patents should appear in this order exactly, then you'll need to deploy them via profile. You don't need to deploy these palettes via profile, but if you do then, when we create copy of the app in profile for the user, the user's going to see exactly what we see right here. So if did want them to come in a different order, reorder them now before we write them out again. Just make sure they're in the correct order for you.

OK so we're going to do next is we going to create a little tool to run a macro. So this time, instead of clicking and dragging a tool from our standard, we're going to create a tool from an existing AutoCAD command. So the command we're going to use the script command, and to find that we're just going to right-click somewhere here over the palette. And we're looking for customized commands. Who's used this workflow before, customized commands? What we should see, we should see this open up a little mini version of the CUI, with a whole big long list of commands that we could add to our palettes.

So what got me really excited about this is we don't just standardize buttons that allow us to create geometry. We can standardize the order in which we want people to work. So I created a bunch of tools for surveying, in which we had our surveying tools in the correct order, to remind people when you do surveying, I want you to put grids down, I want you to draw the drawings, I want you to do annotations, I want you to make notes. We had a separate set of palettes for CNC work. Again, given the correct tools in the correct order I wanted people to use them.

So it's not just the output we can standardize, it's the method. OK so I'm going to search in here for the command I'm looking for. I'm looking for the script command. I have to learn I can't speak and type at the same time. Right. So it's right here, run script. So now it's going to click and drag run script onto my tool palette, and then we can close down the custom user interface. OK. So we have just a standard button. Just going to run a script. OK, you can do that bit if you haven't had a go already.

Yeah so do you just want to just create that one button for me. And then I'll show what to do next. You're not diving machine, so I guess you are up to speed, good. So what we'll do next is we're just going to edit the script to run a little macro that's just going to open up our CAD standard. So right click and choose Properties. I'm going to give it a name, CAD standard. Under description I'm going to say, "opens the CAD standard in your browser." And then down here, where it says Command String. Let me make that a bit bigger so you can see it.

So the command string is a sequence of commands that AutoCAD is going to run when we click on this button. So currently, the command stream just says script. Well let's delete that out of there. And you might find it easy just to copy and paste this in off the handout. So if I catch up, find us on the right page There's a little one line macro in here. OK, so we're looking for this line here on page 19. So if you just want to copy that entire line into the command string. So I'm going to jump back here into AutoCAD and paste that in.

So he's used these kind of macros before? Couple of people. So what does the "carrot C carrot C" a the beginning mean? Dos anyone know? Cancel, cancel, it's equivalent to pressing the escape key twice. So it's going to cancel out any commands that are currently running. Does anybody know what the underscore means? The underscore is localization, right? This is saying, use the standard English version of this command. So this macro would still work if it was an AutoCAD product that had language pack installed. The secret full stop after that. Does anybody know what the secret full stop does? Don't tell your users what the secret full stop does.

The secret full stop will run this command even if it's been undefined. So you can undefined commands in AutoCAD, which means people can't use them. But if you put a full stop in front of it, it will run anyway. So that's an extra tip. You'll see that, and Robert Green does a great class showing you how to get rid of commands you don't want people to use. The command browsers is gonna open up your default internet browser, whatever browser is in the machine. And then we're parsing that command to path, and the path goes to our resources folder, and it's going to open up a PDF called CAD standards.

OK one last tip. We can make the button image look a bit more interesting. So instead of this script image, we're just going to right click over the image and say Specify Image. And included an image for you in the data set. So you can click Specify Image and then browse out again to the C drive, palettes, resources, and I've put a PNG file in here called CAD standard. So we can use this as the image for both the light and the dark theme.

So I'm going to pick Open, and then I will do it again for the dark theme image, pick the same CAD standard icon, and pick Open again. And when we're done, we can pick OK, and that should apply that image to this button. So it's fairly straightforward to create your own button images and have something a bit more intuitive for your users take a look at. So when we're done, we can pick OK, and we'll test it. So let's see what happens. Woo, it work.

So your users have no excuse. Did you read the CAD standard? It's there, you just press the button. There it is, no excuses. Yeah, so we can use tool palettes to standardize our output, we can use it to standardized the method, and we can give people descriptions of exactly what they should be doing. OK so have a go at that if you haven't had a go already. I'll give everybody a minute just to catch up.

Is everybody up to speed? Does anybody need some help? All good? Good, well done. OK, at this point, I did say we'll close AutoCAD to write out change and see what happens, but we're running a little bit behind. So I think I'll wait till the next section, and then we'll close AutoCAD and see what happens. But for the time being, I want to move on to the next bit. So who here uses the action recorder tool? I think the action recorder tool is very useful for CAD managers, because you don't have to get into heavy scripting and lisps to be be able to put together commands that people use the whole time. If you want to put two or three commands together, save people a few clicks if they're doing the same two or three things all the time, the macro recorder is a much easier way of doing it than having to work out the correct macro to write or script to write.

So there's a little bit a set up we need to do here. We need to start by going back to the options. So I'm going to pull up my options again. And we are looking for the action recorder settings, action recording file location. So this is currently set to your local drive, so we want to put this one on the server as well. So when we create action recorder programs, they'll be written out to the server, and then anybody else can use them at same time.

So as we did before, I'm going to click right here, and I'm going to choose Remove. I'm going to remove the standard file. Standard file location is pointing at my local drive. And I click Browse, and point this out to our same C drive, palettes. And I'm going to point it to my support folder, which is where I put all my customizations. Yeah, so when we create our command macros, they're going to be pointed here. Our action recorder macros. Yes, everybody with me?

So we can click Apply, and then we're ready to write a macro. Is anybody here not a CAD user? Like, you're just a CAD admin or kind of IT? Everybody's done on a bit of AutoCAD? Good, this is the only bit of AutoCAD we're going to do in this class, right, so it's not too difficult. If you could open up for me the file here called circular viewport. And we're going to create our action macro using this file right here. So we're going to open that one up.

OK, I'm just going to set my layer back to zero. Right, so you might want to watch this bit the whole way through, and I'll just demonstrate the whole thing creating an action macro. So I'm going to start by going across to the manage tab. And up here I've got my record button. So I'm going to tell AutoCAD I want it to record the steps I'm working on. So I click Record, and I'm ready to start my macro. So my macro is going to change the layer to my viewport layer, and then I'm going to create a circle.

So C enter. And right now it doesn't matter where we put the circle or how big we make it. So start the macro. Change the later view ports. Draw a circle. Now I to create a viewport that's cropped to this circle. So I'm going to end view, to create a viewport, and press Enter. And then to use the circle, I'm going to choose down here-- looking at the command line, what options have I got? I've got the object option. So o for object. And for my object, I'm going to click the last object.

So the last object that was created so, L enter. Yep, and it's turned that circle into a viewport. So now I'm ready to go back to my manage tab and click Stop, and that will create my action macro. Does that makes sense everybody? Yeah, so create that macro, and then, when you're done, I'm just going to rename that circular viewport. And we should see it's going to create this macro in the location C palette support folder. So we're about back on time, so give me a couple of minutes to have a go at that.

Looks like most of you are there. So when you're done, you can pick OK. So you've now got your macro, but we don't have a button to run the macro. So the next step is we have to create a button on our tool palette, and then we can ask that button to run this macro. So the next step is exactly the same as we did before. Right click, customize commands. I'm just going to type in "script," and then left click and drag run script onto my palette. So we're going to create this command that we can point at the action we call the macro.

So once we have our button ready, we're going to follow the same steps again as before. We'll right click over our new button, we'll choose Properties, and we'll change the properties. So I'm going to call this button circular viewport as well. I'll give it a description, "creates a circular viewport on the v ports layer." Yep, so they don't have to remember which layer they're supposed to draw it on. They don't have to remember anything else. They just have to choose the right button. If you've used action recorder macros later, you could refine this by allowing them to pick their own centerpoint and their own radius, but that's another class.

Once again, I've given you an image. So you can right click over image and choose Specify Image. And in the same folder, we'll find something called circular viewport icon. So you can try that out. And I'll set that for both the light and dark theme. And then once again, there's a command macro to run this in the handout. So I'm just going to copy and paste it over. All right so we just need a button to say circular vport. So as long as we name the command string the same as the macro, it should just run.

So once you've created your button, we can delete the existing viewport and then test our button out and see if it works. All right. AU rocks. How are you going on? Well done everybody. It's looking good. So those of you who have managed to successfully create your script, we can close AutoCAD down now and write those changes out. So I'm going to close the circle vport file, close AutoCAD. And if we go and take a look at our build folder now, we should see we've built three tool palettes. So now we've got our CAD standards, palette, our drawer, and our library. And we should also see we have an extra folder called Images.

So AutoCAD didn't use that image we gave it. It actually created a copy of that in this Images folder. Yes and now this folder needs to go out when we move these folders across, because that's where it's going to find these images. Cool, I'm just going to get AutoCAD booting up again. So what we've done so far is we've created some new palettes, we've created a few tools just to test this out. So we're about ready now. This is our standards, done. It's really simple work we do. We just draw circular viewports, that's what we do in our company.

So now we're going to start deploying these tool palettes out. So we want to have a copy out on the server, but we know that we don't want our users to be using this copy, because this copy is going to be read-write. This is the copy that we can continue to edit and continue adding tools to. So we want to create another copy for our users to use. So all we'll do here is we'll go back out to Windows Explorer, and in our palettes folder-- right, so in palettes, build, we're just going to grab a copy of everything that's in here, and we're going to create a copy in our deploy folder.

And then what we'll do is we'll lock these palettes and then we'll point our users at the lock set. And we'll point people to the right set by changing profiles. So what I'm going to do is copy the palettes folder and the catalog. So I'm going to right click here and choose copy, and I'm going to go to my deploy folder and right click in here and choose paste. Yeah that's all we need to do is just copy and paste the copy into our deploy folder. Yeah, So the build copy is ours. The deploy copy is for everybody else.

And the last step is to lock these. So if you could double click into your deploy folder, and what we'll do is we'll just take these individual files that represent each palette, these ATC files, and I'm just going to control left click on all three. And I'm going to right click and choose Properties. And under Properties, we're just going to tick read-only. This is not going to stop your users coming across here and unticking read only, but we're not going to tell them they can do that. And so far nobody's been inquisitive enough to try, right?

Now. Once they appear-- Chad did you get the chance to try this out? When I set these up years ago, I tried setting the whole folder to be read only. And AutoCAD didn't like it. It wouldn't work. I found I had to set the individual palette files to be read-only. That worked. Chad would say he deploys over a network and the entire folder location is read-only to his users, and that works fine. So you might need to test that little bit. I've put in the handout to make the ATC files themselves read-only, but you can test it and give me some feedback. Let me know if that works.

So once you've made them read-only, we can click OK And if we jump back into AutoCAD, so the final step here is to create a user profile and point the user profile at the deploy set. So we'll go back to options, and we'll go along to our profiles tab. So in our profiles tab, we want the exact copy of the admin profile we've just created, but it's going to be called user.

So what we'll do is we'll choose add a list create a new profile called user. And this will just have all the same settings, it's just a direct copy of what we got currently, and choose apply and close. Now once again don't forget which profile is current. Let's take a look at top of the palette. The admin profile, right? So before we do anything else, we need to switch to our user profile. So I'll select user with a left click. I'll choose set current, and we should now see user at the top.

So now we know the user profile is active. Then we go to the files, and we're just going to change this one location, tool palette file location. We do not want them using our build palettes. We want them using the deploy set. So we're just going to change this one path. I'll click browse. I'll browse out to my C drive, palettes, deploy, and pick OK. So now I'm just pointing them at the deploy set. So we'll know if we got this right. I'm just going to shift the options palette over a little bit. I'm going to click Apply. And we should see a little flicker as AutoCAD takes the build set out of memory and loads in the deploy set.

And check this out. Who can see this down here? It's a little padlock telling us these are now locked. You can do what you like to these, but when you close AutoCAD, no changes will be written out. So they can mess around with him to their heart's content, but they're not going to break anything. Exactly. So the question was the lock is coming from the fact it's read-only. So AutoCAD interprets that as a locked palette.

Yes, I actually put both sets on the network. So I have to build set on the network, but just don't tell anybody, the deploy set. One of the other reasons I did it this way because I also had to push standards out to people with laptops, who were going to go and work mobile, who didn't have access to the server. So I could just put this entire set on their C drive and set it up the same way. Good, does that makes sense to everybody? Have you all had a go at that? You all set up your second profile? I can see some nodding. Yes sir?

AUDIENCE: [INAUDIBLE]

PAUL MUNFORD: So the question was, what if we're not using profiles. And I'll tell you what, why don't we come back to that one at the end, because that will take me a few minutes to answer. OK, so I'm just going to click OK. And we can move on to the next step.

So currently we got these two profiles, and they're loading in different sets of palettes. So this is pretty good. But we don't want to have to go around every single user's machine and set them looking at this other set of palettes, right? We want a way of pushing out which profile they should be using. And we're going to do that with a file called the Acad.lsp file. So who's played around with the Acad.lsp file before? Few people.

So the key thing about the Acad.lsp file was two key things. One is, it doesn't exist. You have to create it yourself. So you won't find it in the AutoCAD support path. We're going to create it. The second thing is it loads every time you load AutoCAD. So it's a LISP file. It loads. We can put some LISP code in there and make AutoCAD do stuff. But it does have to live locally to AutoCAD, so it lives on your user's machine. So the best thing to do is to put it in your deployment and roll it out of the deployment. And then you don't have to go and install it manually on everybody's machine.

I can see Chad nodding. How many offices have you got, Chad? 21 offices, right? So he's not going to go around every office and install this for 200 people. So this needs to go into your deployment. So let's do that first, and then what we're going to do is we're going to make our Acad.lsp file load an initialization file. And initialization file will sit on the server, and we can edit that any time we like, because we know the next time our user closes and opens AutoCAD, they'll read in any change from initialization file. So the Acad.lsp file is local, but it grabs the LISP file off the network and loads in whatever we want them to load it.

So we can close down AutoCAD for this bit. And we going to go to our support folder. Actually no, we're going to go to our-- just have to remember this path. We need to go to a local drive, I saw it in the handout. Here we go. Right, so we need to go to our local drive. So C drive, users. We're going to be going into mainframe 2. This is the username for all the machines. So it'll be username, in this case mainframe 2. We are going to app data. So I don't see app data, so I'm going to have to just go to view up here, show hidden items. I'll just pause that there for a second so anybody can see it.

So the app data folder is a hidden folder, so you may need to go to View, tick show hidden items. So we're going to add data. Where is it? Roaming, Autodesk, AutoCAD 2018, r22, emu, support. Were there, right. So this is where we need to create our Acad.lsp file. So the Acad.lsp file is actually just a text file, and we're just going to rename it Acad.lsp So you can right-click anywhere here and say new text file, new text document, but we're going to call it Acad.lsp. And you do need to make sure that it's a Acad with a capital A, and a lowercase c a d. Acad.lsp, and make sure that you've deleted the TXT extension off the end, here.

We'll know if we got it right, because when we press Enter, it should change its icon. Yeah, so it should now have an icon showing at LISP file. Does that make sense? Cool. Now we can open this with a regular text editor. It doesn't need anything fancy. So I'm just going to double left click. And we're going to put a little bit of code in here. And again, it's in the handout, so I'm just going to copy and paste it across. So the code right here, I'm just going to copy this out. Do make sure you don't have any additional spaces or anything that gets copied across.

So how many people have used LISP before? Cool, quite a few. Brilliant. So for those you haven't, the little semi-colon on the front there just means it's a comment, so that's just a line of descriptive text just to tell you what's going to happen. So what we're doing here, is we're creating a path, and the path is looking at our C drive public support folder. Do you know why I've got double forward slash double backslashes in there?

Because that's what works. I can't remember exactly what I need to do. I'll ask Richard later, right? So if I put in just a single slash, AutoCAD would interpret that as a pause in macro language. So we've put in a double slash, or sometimes it's a forward slash, but I can never remember which is which. And it's basically saying, if you can find a file called init.lsp, then run the file called init.lsp. So that's all the code we need, because all the difficult stuff is going to be in the initialization file, the init.lsp file.

So back in my text file, I'll just click OK to click file and save. And then close it down. So I've already created the initialization file for you. So it's here in our support folder, C palettes support, init.lsp. So this is the one that sits on the server that we can change any time we like. And in here put some code in. So this code, firstly it's going to load the object orientated method of doing visual LISP, and then it's going to go out into the network, find a profile called user. And if it can find it, it's going to set it active, which I should have asked you to export already. But there's one in there, so we'll see how we get on.

So going back to the question, if we don't use profiles, you don't have to use profiles. You can set all the paths up in the initialization file and just point people to the right locations. You can actually write out the entire support paths into one big long list of code. And that's the article that Richard wrote that I say that I base a lot of this on. The main reason I showed you profiles is because it remembers the pilot order, and it also remembers palette grouping, which we can't do any other way.

OK, so we can close this down, and let's fire up AutoCAD and see what happens. So if you see this dialog, that's fine. So we can just say, Yep, I'm going to load this. I've got no problems with that loading. And then at this point, if it stops it's because we haven't created the user profile yet. Oh it's loaded. Brilliant.

Good. So hopefully that's given you an idea of how you might deploy these without having to attend everybody's machine. Create the Acad.lsp file, roll it out as part of your deployment, get it to load in this initialization file, get the initialization file to do the hard work. Remember, you can go in and change this initialization file whenever you like. So if there's ever anything you need to set in AutoCAD, whenever AutoCAD opens, you can write a little bit of code in the initial file, and you can control everybody's machines. So every time they open it up, you've reset anything which they fiddled around with which they shouldn't.

Good so we needed that one last step. We've had some good ideas, and now we want to edit our tool palettes and redeploy a new set. So what we need to do, firstly, is open up our options, go to our profiles, and set the admin profile back to being current. So I'll just pick set current here. And again, you'll see your tool palettes flicker as the admin profiles it loaded.

So now we're back into our read-write set of palettes, so we can create a new tool. So maybe, just to demonstrate this, maybe I'll just copy my line tool to my CAD standards tool, just so we can see a difference. Now, there's one tip which I forgot to give you earlier, which I'll demonstrate now. Has anybody ever found that when they've been creating their palettes, you've reordered the tools?

So maybe I'll say, oh, I wanted to have my line tool the top. So I left click and drag, put it at the top. But when you close the palette and open again, they appear in the wrong order. They appear in the initial order. I can see one person nodding. That's good. So here's the tip. If you change the order, if the tool is in your palette, what I'd like to do is left click somewhere over your pilot to make sure it's active, hold down Control and A, which is Select All, and then Control X, cut. They disappear, but don't panic, it's fine. And then control v, and paste them back onto your palette again. Paste.

Is this because we're running on frame, and there's no control v? Awesome, I just made everybody get rid of their work. Trust me, that will work when you get back to the office. All right I just created an extra couple of tools there. OK so, to save our changes, we know we've got it close to close AutoCAD. So we'll need to shut AutoCAD down again to write those changes out. And I'm going to go back to my palettes folder, into build, and I'm just going to copy those again, just as we did before.

So copy, go back to my deploy folder, paste. I'm just going to write them over the top. Straight over the top of the ones that are there already. And then we just need to remember to go back into the palettes folder, grab those palette files, and lock them. And we can do this whilst the users are still using AutoCAD, because they're not going to see this change until they shut down AutoCAD and open again. It'll reload in a fresh set of palettes.

So we can do this on the fly. We don't have to wait for til everybody's gone home for the evening, or do it the weekend. We can do during the day when it's sociable. So if you got that step OK, you can pick OK and you can fire up AutoCAD again. And we hope the Acad.lsp will kick in, it will load the initialization file and set the user profile current again. And we should see our updated set of palettes come across. No, it's not user profile current. Oh well.

OK, I kind of cheated there and just switched it across manually. But I switched back to my user profile, and we can see our tools have loaded in our locked palette. Fantastic. How was that for everybody?

So our objectives, how do you think we did? Easy to set up. Is everybody confident they can do that when they get back to the office? Easy to deploy, it's just a copy and paste. That's pretty easy. Easy for our users to use. Hopefully we should say that, OK. And easy to update. Easy to migrate. [INAUDIBLE] When did tool palettes come out? 2009? 2004? So year on year, I found there were no changes to tool palettes between about 2007 to 2017. And when I moved over from 2017 to 2018, a couple of my tools broke.

So tool palettes are really easy to migrate, because they very rarely change them. So I'm going to give it a tick there. OK, so some questions for you. Why don't we just stick the palettes on the server and just let everybody access them? Because they get overwritten, exactly. So AutoCAD saves changes to tool palettes on close. Last out wins. So if we just stuck them on the server and everybody had access to them, whoever shut down last, end of the day, would all get their tool palettes in the morning.

Which variable allows us to save palettes in a custom location? I've not mentioned it. It's in the handout. Has anybody read that? So the variable we changed, using the support files, is actually *ToolPalettePath. You'll see it in the handout. So you don't have to change it with profiles. You can change it with a script. You can change it with a macro. You can change it with some LISP.

So if you're using AutoCAD LT and you don't have profiles, you might want to use a little macro to change which palettes are loaded. So I've put some information about that in the handout as well. Which LISP file loads when we opened AutoCAD? Acad.lsp, yeah. And how do we lock the tool palette ATC files? Read-only. Only We just made them read-only. Perfect.

Thank you very much, everybody. Please don't forget to fill out your surveys, your class surveys. I really appreciate you spending time, and if you do have the time to write a comment, I really appreciate that. Any questions from anybody? Sir?

AUDIENCE: [INAUDIBLE]

PAUL MUNFORD: So the question was, what do you do if everybody's not connected to the server, could use something like Dropbox? I see no reason why you couldn't use something like Dropbox. But, I'm not sure how you'd force a refresh on Dropbox. So if you put some new files in there, how long is it going to take for your files to populate? So I'd say go and chat to Chad about that one afterwords, because he's got a lot of offices to deal with. Does anybody else have a question?

AUDIENCE: [INAUDIBLE]

PAUL MUNFORD: I believe there is.

AUDIENCE: [INAUDIBLE]

PAUL MUNFORD: Yes I think so, yeah. Thank you very much, everybody. Enjoy AU.

______
icon-svg-close-thick

Cookie 首选项

您的隐私对我们非常重要,为您提供出色的体验是我们的责任。为了帮助自定义信息和构建应用程序,我们会收集有关您如何使用此站点的数据。

我们是否可以收集并使用您的数据?

详细了解我们使用的第三方服务以及我们的隐私声明

绝对必要 – 我们的网站正常运行并为您提供服务所必需的

通过这些 Cookie,我们可以记录您的偏好或登录信息,响应您的请求或完成购物车中物品或服务的订购。

改善您的体验 – 使我们能够为您展示与您相关的内容

通过这些 Cookie,我们可以提供增强的功能和个性化服务。可能由我们或第三方提供商进行设置,我们会利用其服务为您提供定制的信息和体验。如果您不允许使用这些 Cookie,可能会无法使用某些或全部服务。

定制您的广告 – 允许我们为您提供针对性的广告

这些 Cookie 会根据您的活动和兴趣收集有关您的数据,以便向您显示相关广告并跟踪其效果。通过收集这些数据,我们可以更有针对性地向您显示与您的兴趣相关的广告。如果您不允许使用这些 Cookie,您看到的广告将缺乏针对性。

icon-svg-close-thick

第三方服务

详细了解每个类别中我们所用的第三方服务,以及我们如何使用所收集的与您的网络活动相关的数据。

icon-svg-hide-thick

icon-svg-show-thick

绝对必要 – 我们的网站正常运行并为您提供服务所必需的

Qualtrics
我们通过 Qualtrics 借助调查或联机表单获得您的反馈。您可能会被随机选定参与某项调查,或者您可以主动向我们提供反馈。填写调查之前,我们将收集数据以更好地了解您所执行的操作。这有助于我们解决您可能遇到的问题。. Qualtrics 隐私政策
Akamai mPulse
我们通过 Akamai mPulse 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Akamai mPulse 隐私政策
Digital River
我们通过 Digital River 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Digital River 隐私政策
Dynatrace
我们通过 Dynatrace 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Dynatrace 隐私政策
Khoros
我们通过 Khoros 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Khoros 隐私政策
Launch Darkly
我们通过 Launch Darkly 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Launch Darkly 隐私政策
New Relic
我们通过 New Relic 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. New Relic 隐私政策
Salesforce Live Agent
我们通过 Salesforce Live Agent 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Salesforce Live Agent 隐私政策
Wistia
我们通过 Wistia 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Wistia 隐私政策
Tealium
我们通过 Tealium 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Tealium 隐私政策
Upsellit
我们通过 Upsellit 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Upsellit 隐私政策
CJ Affiliates
我们通过 CJ Affiliates 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. CJ Affiliates 隐私政策
Commission Factory
我们通过 Commission Factory 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Commission Factory 隐私政策
Google Analytics (Strictly Necessary)
我们通过 Google Analytics (Strictly Necessary) 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Google Analytics (Strictly Necessary) 隐私政策
Typepad Stats
我们通过 Typepad Stats 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Typepad Stats 隐私政策
Geo Targetly
我们使用 Geo Targetly 将网站访问者引导至最合适的网页并/或根据他们的位置提供量身定制的内容。 Geo Targetly 使用网站访问者的 IP 地址确定访问者设备的大致位置。 这有助于确保访问者以其(最有可能的)本地语言浏览内容。Geo Targetly 隐私政策
SpeedCurve
我们使用 SpeedCurve 来监控和衡量您的网站体验的性能,具体因素为网页加载时间以及后续元素(如图像、脚本和文本)的响应能力。SpeedCurve 隐私政策
Qualified
Qualified is the Autodesk Live Chat agent platform. This platform provides services to allow our customers to communicate in real-time with Autodesk support. We may collect unique ID for specific browser sessions during a chat. Qualified Privacy Policy

icon-svg-hide-thick

icon-svg-show-thick

改善您的体验 – 使我们能够为您展示与您相关的内容

Google Optimize
我们通过 Google Optimize 测试站点上的新功能并自定义您对这些功能的体验。为此,我们将收集与您在站点中的活动相关的数据。此数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID 等。根据功能测试,您可能会体验不同版本的站点;或者,根据访问者属性,您可能会查看个性化内容。. Google Optimize 隐私政策
ClickTale
我们通过 ClickTale 更好地了解您可能会在站点的哪些方面遇到困难。我们通过会话记录来帮助了解您与站点的交互方式,包括页面上的各种元素。将隐藏可能会识别个人身份的信息,而不会收集此信息。. ClickTale 隐私政策
OneSignal
我们通过 OneSignal 在 OneSignal 提供支持的站点上投放数字广告。根据 OneSignal 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 OneSignal 收集的与您相关的数据相整合。我们利用发送给 OneSignal 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. OneSignal 隐私政策
Optimizely
我们通过 Optimizely 测试站点上的新功能并自定义您对这些功能的体验。为此,我们将收集与您在站点中的活动相关的数据。此数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID 等。根据功能测试,您可能会体验不同版本的站点;或者,根据访问者属性,您可能会查看个性化内容。. Optimizely 隐私政策
Amplitude
我们通过 Amplitude 测试站点上的新功能并自定义您对这些功能的体验。为此,我们将收集与您在站点中的活动相关的数据。此数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID 等。根据功能测试,您可能会体验不同版本的站点;或者,根据访问者属性,您可能会查看个性化内容。. Amplitude 隐私政策
Snowplow
我们通过 Snowplow 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Snowplow 隐私政策
UserVoice
我们通过 UserVoice 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. UserVoice 隐私政策
Clearbit
Clearbit 允许实时数据扩充,为客户提供个性化且相关的体验。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。Clearbit 隐私政策
YouTube
YouTube 是一个视频共享平台,允许用户在我们的网站上查看和共享嵌入视频。YouTube 提供关于视频性能的观看指标。 YouTube 隐私政策

icon-svg-hide-thick

icon-svg-show-thick

定制您的广告 – 允许我们为您提供针对性的广告

Adobe Analytics
我们通过 Adobe Analytics 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Adobe Analytics 隐私政策
Google Analytics (Web Analytics)
我们通过 Google Analytics (Web Analytics) 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Google Analytics (Web Analytics) 隐私政策
AdWords
我们通过 AdWords 在 AdWords 提供支持的站点上投放数字广告。根据 AdWords 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 AdWords 收集的与您相关的数据相整合。我们利用发送给 AdWords 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. AdWords 隐私政策
Marketo
我们通过 Marketo 更及时地向您发送相关电子邮件内容。为此,我们收集与以下各项相关的数据:您的网络活动,您对我们所发送电子邮件的响应。收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、电子邮件打开率、单击的链接等。我们可能会将此数据与从其他信息源收集的数据相整合,以根据高级分析处理方法向您提供改进的销售体验或客户服务体验以及更相关的内容。. Marketo 隐私政策
Doubleclick
我们通过 Doubleclick 在 Doubleclick 提供支持的站点上投放数字广告。根据 Doubleclick 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Doubleclick 收集的与您相关的数据相整合。我们利用发送给 Doubleclick 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Doubleclick 隐私政策
HubSpot
我们通过 HubSpot 更及时地向您发送相关电子邮件内容。为此,我们收集与以下各项相关的数据:您的网络活动,您对我们所发送电子邮件的响应。收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、电子邮件打开率、单击的链接等。. HubSpot 隐私政策
Twitter
我们通过 Twitter 在 Twitter 提供支持的站点上投放数字广告。根据 Twitter 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Twitter 收集的与您相关的数据相整合。我们利用发送给 Twitter 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Twitter 隐私政策
Facebook
我们通过 Facebook 在 Facebook 提供支持的站点上投放数字广告。根据 Facebook 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Facebook 收集的与您相关的数据相整合。我们利用发送给 Facebook 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Facebook 隐私政策
LinkedIn
我们通过 LinkedIn 在 LinkedIn 提供支持的站点上投放数字广告。根据 LinkedIn 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 LinkedIn 收集的与您相关的数据相整合。我们利用发送给 LinkedIn 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. LinkedIn 隐私政策
Yahoo! Japan
我们通过 Yahoo! Japan 在 Yahoo! Japan 提供支持的站点上投放数字广告。根据 Yahoo! Japan 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Yahoo! Japan 收集的与您相关的数据相整合。我们利用发送给 Yahoo! Japan 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Yahoo! Japan 隐私政策
Naver
我们通过 Naver 在 Naver 提供支持的站点上投放数字广告。根据 Naver 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Naver 收集的与您相关的数据相整合。我们利用发送给 Naver 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Naver 隐私政策
Quantcast
我们通过 Quantcast 在 Quantcast 提供支持的站点上投放数字广告。根据 Quantcast 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Quantcast 收集的与您相关的数据相整合。我们利用发送给 Quantcast 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Quantcast 隐私政策
Call Tracking
我们通过 Call Tracking 为推广活动提供专属的电话号码。从而,使您可以更快地联系我们的支持人员并帮助我们更精确地评估我们的表现。我们可能会通过提供的电话号码收集与您在站点中的活动相关的数据。. Call Tracking 隐私政策
Wunderkind
我们通过 Wunderkind 在 Wunderkind 提供支持的站点上投放数字广告。根据 Wunderkind 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Wunderkind 收集的与您相关的数据相整合。我们利用发送给 Wunderkind 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Wunderkind 隐私政策
ADC Media
我们通过 ADC Media 在 ADC Media 提供支持的站点上投放数字广告。根据 ADC Media 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 ADC Media 收集的与您相关的数据相整合。我们利用发送给 ADC Media 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. ADC Media 隐私政策
AgrantSEM
我们通过 AgrantSEM 在 AgrantSEM 提供支持的站点上投放数字广告。根据 AgrantSEM 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 AgrantSEM 收集的与您相关的数据相整合。我们利用发送给 AgrantSEM 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. AgrantSEM 隐私政策
Bidtellect
我们通过 Bidtellect 在 Bidtellect 提供支持的站点上投放数字广告。根据 Bidtellect 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Bidtellect 收集的与您相关的数据相整合。我们利用发送给 Bidtellect 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Bidtellect 隐私政策
Bing
我们通过 Bing 在 Bing 提供支持的站点上投放数字广告。根据 Bing 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Bing 收集的与您相关的数据相整合。我们利用发送给 Bing 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Bing 隐私政策
G2Crowd
我们通过 G2Crowd 在 G2Crowd 提供支持的站点上投放数字广告。根据 G2Crowd 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 G2Crowd 收集的与您相关的数据相整合。我们利用发送给 G2Crowd 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. G2Crowd 隐私政策
NMPI Display
我们通过 NMPI Display 在 NMPI Display 提供支持的站点上投放数字广告。根据 NMPI Display 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 NMPI Display 收集的与您相关的数据相整合。我们利用发送给 NMPI Display 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. NMPI Display 隐私政策
VK
我们通过 VK 在 VK 提供支持的站点上投放数字广告。根据 VK 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 VK 收集的与您相关的数据相整合。我们利用发送给 VK 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. VK 隐私政策
Adobe Target
我们通过 Adobe Target 测试站点上的新功能并自定义您对这些功能的体验。为此,我们将收集与您在站点中的活动相关的数据。此数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID 等。根据功能测试,您可能会体验不同版本的站点;或者,根据访问者属性,您可能会查看个性化内容。. Adobe Target 隐私政策
Google Analytics (Advertising)
我们通过 Google Analytics (Advertising) 在 Google Analytics (Advertising) 提供支持的站点上投放数字广告。根据 Google Analytics (Advertising) 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Google Analytics (Advertising) 收集的与您相关的数据相整合。我们利用发送给 Google Analytics (Advertising) 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Google Analytics (Advertising) 隐私政策
Trendkite
我们通过 Trendkite 在 Trendkite 提供支持的站点上投放数字广告。根据 Trendkite 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Trendkite 收集的与您相关的数据相整合。我们利用发送给 Trendkite 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Trendkite 隐私政策
Hotjar
我们通过 Hotjar 在 Hotjar 提供支持的站点上投放数字广告。根据 Hotjar 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Hotjar 收集的与您相关的数据相整合。我们利用发送给 Hotjar 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Hotjar 隐私政策
6 Sense
我们通过 6 Sense 在 6 Sense 提供支持的站点上投放数字广告。根据 6 Sense 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 6 Sense 收集的与您相关的数据相整合。我们利用发送给 6 Sense 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. 6 Sense 隐私政策
Terminus
我们通过 Terminus 在 Terminus 提供支持的站点上投放数字广告。根据 Terminus 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Terminus 收集的与您相关的数据相整合。我们利用发送给 Terminus 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Terminus 隐私政策
StackAdapt
我们通过 StackAdapt 在 StackAdapt 提供支持的站点上投放数字广告。根据 StackAdapt 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 StackAdapt 收集的与您相关的数据相整合。我们利用发送给 StackAdapt 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. StackAdapt 隐私政策
The Trade Desk
我们通过 The Trade Desk 在 The Trade Desk 提供支持的站点上投放数字广告。根据 The Trade Desk 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 The Trade Desk 收集的与您相关的数据相整合。我们利用发送给 The Trade Desk 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. The Trade Desk 隐私政策
RollWorks
We use RollWorks to deploy digital advertising on sites supported by RollWorks. Ads are based on both RollWorks data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that RollWorks has collected from you. We use the data that we provide to RollWorks to better customize your digital advertising experience and present you with more relevant ads. RollWorks Privacy Policy

是否确定要简化联机体验?

我们希望您能够从我们这里获得良好体验。对于上一屏幕中的类别,如果选择“是”,我们将收集并使用您的数据以自定义您的体验并为您构建更好的应用程序。您可以访问我们的“隐私声明”,根据需要更改您的设置。

个性化您的体验,选择由您来做。

我们重视隐私权。我们收集的数据可以帮助我们了解您对我们产品的使用情况、您可能感兴趣的信息以及我们可以在哪些方面做出改善以使您与 Autodesk 的沟通更为顺畅。

我们是否可以收集并使用您的数据,从而为您打造个性化的体验?

通过管理您在此站点的隐私设置来了解个性化体验的好处,或访问我们的隐私声明详细了解您的可用选项。