Notification / Events
-
This question came up during last week's accelerator, and is part of the reason I spent creating the last post: is it possible to selectively unlock certain layers for the duration of commands that have been specified by the user? Let's take an example: you have layers that should remain locked, apart from when using […]
-
This is a problem that developers have been struggling with for some time, and it came up again at the recent Cloud Accelerator: how to control the display of AutoCAD geometry at a per-viewport level, perhaps to implement your own "isolate in a viewport" command. It's certainly possible to control layer visibility at the viewport […]
-
Last week we introduced the ExecuteInCommandContextAsync() method and saw it in action from a context menu click event. In today's post we're going to see how it can be used for a lot more: we're going to use it to respond to external, operating system-level events (although admittedly we're handling the event in-process to AutoCAD […]
-
It's time to start looking in more detail at some of the new API capabilities in AutoCAD 2016. To give you a sense of what to expect in terms of a timeline, this week we'll look at a couple of uses for DocumentCollection.ExecuteInCommandContextAsync() and next week we'll look at point cloud floorplan extraction and (hopefully) […]
-
In this post we're wrapping up this mini-series on docking, which is part of a much broader story arc around a "command-line helper" tool, of course. But then we're reaching the end of that, too, I suspect, as the app's just about done. Hopefully it's ready for posting to Autodesk Labs, at least. Last time […]
-
I'm happy to say that the implementation I mentioned in the last post ended up being pretty straightforward. Which is actually great, as I have some important posts to work on for next week. ๐ Today we're going to take a look at the next stage of the "command-line helper" implementation: basic right-click movement of […]
-
During the course of this week we're going to look at extending the command-line helper sample posted last week by allowing our global keywords window to "dock" to the four corners of the drawing window as well as to remain fixed at a custom location somewhere on the screen. I use the term "dock" here […]
-
Today we're going to look at the implementation talked about in the last post: we're going to see how it's possible to use the Application.PreTranslateMessage() method to hack AutoCAD's message-loop and basically convert typed keywords into global ones. This is actually pretty neat (yes, even if I do say so myself ๐ and frankly I'm […]
-
This post carries on from this series from a couple of weeks ago: Adding a global keyword menu to AutoCAD using WPF โ Part 1 Adding a global keyword menu to AutoCAD using WPF โ Part 2 Enabling global commands on localized AutoCAD versions using .NET The overall goal behind these posts was to create […]
-
Here's a quick piece of code to finish up the week to complement what we saw earlier. The idea is that on localized AutoCAD versions this code will allow the user to enter English commands without needing the underscore prefix. The code works by detecting an "unknown" command and then attempting to execute it again […]