图层操作QAP：
Q：
通过代码修改图层状态（比如开关图层）后，绘图区不能实时更新图层状态，需要鼠标进入绘图区激活屏幕才会刷新，执行 Application.UpdateScreen() 方法也没用。
A：
修改图层状态并提交事务后，先执行 TransactionManager.QueueForGraphicsFlush() ，再执行 UpdateScreen() 即可
P：
注意，如果是调整了图层的冻结状态，需要执行 Editor.Regen() 来重生成才能够正常显示。图元数量大的话，重生成会很慢，导致界面卡顿，谨慎使用。
Q：
可以通过代码很简单的设置当前图层，但系统当前图层改变事件就不那么容易捕捉，LayerTable 中也没有相关事件，最后在外网找到一个方法。
A：
监视系统变量 CLAYER ，可通过订阅 Application.SystemVariableChanged 事件实现。
Q：
图层冻结和删除的限制
A：
当前图层不可冻结，可使用 Database.Clayer 或者 Application.GetSystemVariable(“CLAYER”) 获取当前图层来做比较，判断是否可冻结。
图层0、图层Defpoints、当前图层、有块参照的图层，有实体的图层均不能被删除，进行删除操作之前应注意
好吧，缝缝补补，也不知道今天具体完成了啥，图层管理器已经有个雏形了，各种事件响应、启动加载、界面联动、异常捕捉都基本搞定，右键菜单功能也有了思路，明天继续完善。。。
今天最大的收获应该是一个博客：Drive AutoCAD with Code ，博主是土木工程师出生，起码有个十几二十年的 AutoCAD 开发经验，附个ta的自我介绍：
After graduating from university, I worked as civil engineer for more than 10 years. It was AutoCAD use that led me to the path of computer programming. Although I now do more generic business software development, such as enterprise system, timesheet, billing, web services…, AutoCAD related programming is always interesting me and I still get AutoCAD programming tasks assigned to me from time to time. So, AutoCAD goes, I go.
博客满满都是干货，虽然全英文，而且浏览要翻墙，但完全值得啊，附一篇十年前的博文：
Tuesday, September 28, 2010
Pluggable PaletteSet
In ObjectARX .NET API, AutoCAD.Windows.PaletteSet class makes creating dockable floating winidow in AutoCAD a pretty easy thing to do. Many AutoCAD programmers use PaletteSet as a UI container to host a series of Palettes (Windows Form User Controls, usually).
Prior to AutoCAD 2009, PaletteSet is sealed class, e.g. it cannot be inherited as a base class to derive your own custom PaletteSet. Since AutoCAD 2009, PaletteSet class is not sealed any more. This opens a possiblity for our AutoCAD programmer to create a custom, generic PaletteSet UI container once, and develop pluggable palette based on business need and plug into the PaletteSet when needed (without any code change to the PaletteSet).
In this article, I’ll show how to use interface to define a pluggable PaletteSet. Interface is commonly used to define a set operations/properties for different classes to implement. It is one of the OO programming basic concept and used in .NET programming very often. However, there are many AutoCAD programmers who may not be a professional software developers and may too focused on AutoCAD API itself and did not explore some “advanced” programming technique enough, such as using “Interface” to simplify development tasks.
For this article, I demonstrate how to use Interface to create a pluggable PaletteSet. In Visual Stadio 2008, I started a class library project called MyPaletteSet, which includes 3 code files.
First code file is a interface that defines Palette that will be hosted in the pluggable PaletteSet: IThePalette. Later, when creating a Win Form UserControl as Palette, the UserControl will implement the interface. This, no matter how do you design your UserControls and how different they would be, to the hosting PaletteSet, they all are IThePalette. That is, the hosting PaletteSet does not have knowledge of each individual UserControl it hosts, as long as the UserControl is an IThePalette.
Here is the code:
namespace MyPaletteSet
{
public interface IThePalette
{
ThePaletteSet PaletteSet { set; get; }
string PaletteName { get; }
void Close();
void ClosePaletteSet();
}
}
Second code file is the custom PaletteSet, derived from Autodesk.AutoCAD.Windows.PaletteSet. As aforementioned, it is only possible when you use AutoCAD 2009 or later.
Here is the code:
using System;
using System.Drawing;
using System.Collections.Generic;
using Autodesk.AutoCAD.Windows;
using Autodesk.AutoCAD.ApplicationServices;
namespace MyPaletteSet
{
public class ThePaletteSet : PaletteSet
{
private static Guid _guid =
new Guid("B9169E25-3EC1-442F-B518-46B2DA174A2F");
private DocumentCollection _dwgManager = null;
private List<IThePalette> _paltettes = new List<IThePalette>();
public event DocumentCollectionEventHandler DwgBecameCurrent;
public ThePaletteSet()
: base("ThePaletteSet",null, _guid)
{
this.Style = PaletteSetStyles.ShowAutoHideButton |
PaletteSetStyles.ShowCloseButton |
PaletteSetStyles.Snappable;
this.Opacity = 100;
this.Dock = DockSides.None;
this.DockEnabled = DockSides.None;
this.Size = new Size(500, 400);
this.MinimumSize = new Size(250, 200);
_dwgManager = Autodesk.AutoCAD.ApplicationServices
.Application.DocumentManager;
//Handle DocumentCollection events to bubble up the event for IThePalette
_dwgManager.DocumentBecameCurrent +=
new DocumentCollectionEventHandler(_dwgManager_DocumentBecameCurrent);
}
private void _dwgManager_DocumentBecameCurrent(
object sender, DocumentCollectionEventArgs e)
{
if (DwgBecameCurrent != null)
{
DwgBecameCurrent(this, e);
}
}
public void AddPalette(IThePalette palette)
{
bool exists = false;
foreach (IThePalette plt in _paltettes)
{
if (plt.PaletteName.ToUpper() == palette.PaletteName.ToUpper())
{
exists = true;
break;
}
}
if (!exists)
{
System.Windows.Forms.Control ctl =
palette as System.Windows.Forms.Control;
//Add to paletteset
this.Add(palette.PaletteName, ctl);
_paltettes.Add(palette);
palette.PaletteSet = this;
}
}
public void RemovePalette(string paletteName)
{
if (_paltettes.Count == 0) return;
for (int i = 0; i < _paltettes.Count; i++)
{
if (_paltettes[i].PaletteName.ToUpper() == paletteName.ToUpper())
{
System.Windows.Forms.Control ctl =
_paltettes[i] as System.Windows.Forms.Control;
this.Remove(i);
_paltettes.RemoveAt(i);
ctl.Dispose();
if (_paltettes.Count == 0) this.Visible = false;
return;
}
}
}
public void ActivatePalette(string paletteName)
{
if (_paltettes.Count == 0) return;
for (int i = 0; i < _paltettes.Count; i++)
{
if (_paltettes[i].PaletteName.ToUpper() == paletteName.ToUpper())
{
this.Activate(i);
return;
}
}
}
}
}
Pay attention to this line of code:
public event DocumentCollectionEventHandler DwgBecameCurrent;
and this line of code:
_dwgManager.DocumentBecameCurrent += new …
Some of your Palettes may be designed to handle drawing based data. Since PaletteSet is a floating/modeless window, when current drawing changed in AutoCAD, the data shown in certain palette should be refreshed because of current drawing change (like AutoCAD’s “Properties” window). Therefore, the this type of palette must be able to handle various events originally raised by DocumentCollection. So, here I simply handle the DocumentCollection events in the custom PaletteSet and bubble the events up. It is up to the individual Palette to subscribe the events when necessary. To simplfy the example, I only handle and raise the DocumentBecameCurrent event. In real production code, we could bubble up all the DocumentCollection events. The third code file is contains a static help method to create an instance of the custom PaletteSet. Here is the code:
using Autodesk.AutoCAD.Runtime;
[assembly: ExtensionApplication(typeof(MyPaletteSet.ThePaletteSetInitializer))]
namespace MyPaletteSet
{
public class ThePaletteSetInitializer : IExtensionApplication
{
private static ThePaletteSet _paletteSet = null;
public void Initialize()
{
//If necessary, add some code
}
public void Terminate()
{
if (_paletteSet != null) _paletteSet.Dispose();
}
public static ThePaletteSet CreateThePaltetteSet(IThePalette palette)
{
if (_paletteSet == null)
{
_paletteSet = new ThePaletteSet();
}
//Add palette to the PaletteSet
_paletteSet.AddPalette(palette);
return _paletteSet;
}
public static ThePaletteSet CreateThePaltetteSet()
{
if (_paletteSet == null)
{
_paletteSet = new ThePaletteSet();
}
return _paletteSet;
}
}
}
That’s it. Now we have a generic, pluggable PaletteSet. Build the project. From now on, when you want to build a suite of your own tools that have UI to be hosted in a PaletteSet, you can focus to the development of the Palette (Win Form UserControl) and never need to update the PaletteSet host and redeploy it. Let’s see a couple of sample palettes. Sample 1: FirstPalette. Start a new class library command. It can be in the same solution as the “MyPaletteSet”. But to better understand the “pluggable” nature, it is recommended to do this project in different solution. This will show that you can really focus on developing your Palette without having to update the PaletteSet at all. Once the project created, set reference to the DLL generated in “MyPaletteSet” project (MyPaletteSet.dll). Add a Win Form UserControl, called FirstPalette. It looks like:
Here is the code of the UserControl:
using System;
using System.Windows.Forms;
using Autodesk.AutoCAD.ApplicationServices;
using MyPaletteSet;
namespace FirstPaletteTool
{
public partial class FirstPalette : UserControl, IThePalette
{
private ThePaletteSet _parent = null;
public FirstPalette()
{
InitializeComponent();
Document dwg = Autodesk.AutoCAD.ApplicationServices.
Application.DocumentManager.MdiActiveDocument;
if (dwg != null) txtFileName.Text = dwg.Name;
}
#region IThePalette Members
public string PaletteName
{
get { return "First Palette"; }
}
public ThePaletteSet PaletteSet
{
get
{
return _parent;
}
set
{
_parent = value;
_parent.DwgBecameCurrent +=
new DocumentCollectionEventHandler(
_parent_DwgBecameCurrent);
}
}
void _parent_DwgBecameCurrent(object sender,
DocumentCollectionEventArgs e)
{
txtFileName.Text = e.Document.Name;
}
public void Close()
{
if (_parent != null)
{
_parent.RemovePalette(this.PaletteName);
}
}
public void ClosePaletteSet()
{
if (_parent != null) _parent.Visible = false;
}
#endregion
private void button2_Click(object sender, EventArgs e)
{
this.ClosePaletteSet();
}
private void button1_Click(object sender, EventArgs e)
{
this.Close();
}
}
}
Then add another class file into the project: FirstPaletteCommand. Here is the code:
using Autodesk.AutoCAD.ApplicationServices;
using Autodesk.AutoCAD.Runtime;
using MyPaletteSet;
[assembly: CommandClass(typeof(FirstPaletteTool.FirstPaletteCommand))]
namespace FirstPaletteTool
{
public class FirstPaletteCommand
{
private static ThePaletteSet _pltSet;
[CommandMethod("StartFirst", CommandFlags.Session)]
public static void RunThisMethod()
{
Document dwg = Application.DocumentManager.MdiActiveDocument;
try
{
FirstPalette plt = new FirstPalette();
_pltSet = MyPaletteSet.
ThePaletteSetInitializer.CreateThePaltetteSet(plt);
_pltSet.Visible = true;
_pltSet.ActivatePalette(plt.PaletteName);
}
catch(System.Exception ex)
{
dwg.Editor.WriteMessage("\nError: " + ex.Message);
}
}
}
}
Since I want this palette to show per-drawing based data, thus, I make this palette subscribe event “DwgBecameCurrent” raised by the hosting PaletteSet (MyPaletteSet). As you can see, no matter what UI components you place onto this palette (UserControl) and what code logic you will let this palette to execute, you can plug the palette into a common PaletteSet easily. New, let me create another palette: SecondPalette. Start a new class library project, called “SecondPaletteTool”, set reference to “MyPaletteSet.dll”. Add a Win Form UserControl, which looks like:
Its code is here:
using System;
using System.Windows.Forms;
using MyPaletteSet;
namespace SecondPaletteTool
{
public partial class SecondPalette : UserControl, IThePalette
{
private ThePaletteSet _parent = null;
public SecondPalette()
{
InitializeComponent();
}
#region IThePalette Members
public ThePaletteSet PaletteSet
{
get
{
return _parent;
}
set
{
_parent = value;
}
}
public string PaletteName
{
get { return "Second Palette"; }
}
public void Close()
{
if (_parent != null)
{
_parent.RemovePalette(this.PaletteName);
}
}
public void ClosePaletteSet()
{
if (_parent != null) _parent.Visible = false;
}
#endregion
private void button1_Click(object sender, EventArgs e)
{
this.Close();
}
private void button2_Click(object sender, EventArgs e)
{
this.ClosePaletteSet();
}
}
}
Notice that this palette does not subscribe event raised by hosting PaletteSet. Add a class into the project: SecondPaletteCommand:
using Autodesk.AutoCAD.ApplicationServices;
using Autodesk.AutoCAD.Runtime;
using MyPaletteSet;
[assembly: CommandClass(typeof(SecondPaletteTool.SecondPaletteCommand))]
namespace SecondPaletteTool
{
public class SecondPaletteCommand
{
private static ThePaletteSet _pltSet;
[CommandMethod("StartSecond", CommandFlags.Session)]
public static void RunThisMethod()
{
Document dwg = Application.DocumentManager.MdiActiveDocument;
try
{
SecondPalette plt = new SecondPalette();
_pltSet = MyPaletteSet.
ThePaletteSetInitializer.CreateThePaltetteSet(plt);
_pltSet.Visible = true;
_pltSet.ActivatePalette(plt.PaletteName);
}
catch (System.Exception ex)
{
dwg.Editor.WriteMessage("\nError: " + ex.Message);
}
}
}
}
As you can see, no matter how different the second palette from the first one, it can be plugged into MyPaletteSet in the same way, because, to MyPaletteSet, these 2 palettes are the same type: IMyPalette.
Now, start AutoCAD and “NETLOAD” the 2 palette projects (e.g. load FirstPaletteTool.dll and SecondPaletteTool.dll separately, as if the 2 DLLs are deployed and loaded separately). Enter command “StartFirst” and/or “StartSecond”. You can see the corresponding palette will be shown in a common PaletteSet. If you open more than one drawings in AutoCAD and switch the active drawing, you can see the file name shown on the “First Palette” changes accordingly, because this palette handles DwgBecameCurrent event raised by the hosting PaletteSet.
From now on, whenever I want to develop a new AutoCAD tool that would have a modeless window as UI, I can go ahead to develop the UI as Win Form UserControl. Once it is done, I can simply plug it into the common hosting PaletteSet. Since the newly developed palette is in its own project, it can be deployed independently to all existing palettes, yet they are hosted in the same PaletteSet.
In the FirstPalette, I have to add “using Autodesk.AutoCAD.ApplicationServices;” because the palette has to comsume DocumentCollectionEventArgs in the DwgBecameCurrent event handler. In real development code, it is best practice to not let the UserControl to be tied to AutoCAD’s dll. In this case, it is better to define my own custom EvenArgs and my own custom EventHandler in the MyPaletteSet project and use them to bubble up the various DocumentCollection events.
以上就是全文，亲测可用，Good Night
扫一扫
2315
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
