Community
Most if not all of the entity selection methods are under the Editor object in the EditorInput namespace.
I didn't try, but I'm sure if you search this forum for entity selection, you'll find plenty of examples.
I didn't try, but I'm sure if you search this forum for entity selection, you'll find plenty of examples.
Dave O. 
The EditorInput Namespace is located in acmgd.dll. If you have that referenced, maybe Norman is right about what you are trying to do?
Dave O.
Have you read my reply?
You CANNOT use EditorInputs namespace or set reference to acmgd.dll in your Windows exe application. Many topics discussed in this NG sipmly do not appy to you. This NG is meant for ObjectARX .NET APIs, while your exe app can only talk to AutoCAD via COM APIs, in spite you use C#. So, unless you change your whole design (automating AutoCAD through an external exe app), you can only look into COM object model's AcadSelectionSet.Select() method, as you do in VBA, well, if you have VBA experience
As matter of fact, running an exe application, and ask user switch to AutoCAD to select something in AutoCAD screen, is really not a favoured approach, to say the least, I'd say it is rather bad approach in most cases.
You CANNOT use EditorInputs namespace or set reference to acmgd.dll in your Windows exe application. Many topics discussed in this NG sipmly do not appy to you. This NG is meant for ObjectARX .NET APIs, while your exe app can only talk to AutoCAD via COM APIs, in spite you use C#. So, unless you change your whole design (automating AutoCAD through an external exe app), you can only look into COM object model's AcadSelectionSet.Select() method, as you do in VBA, well, if you have VBA experience
As matter of fact, running an exe application, and ask user switch to AutoCAD to select something in AutoCAD screen, is really not a favoured approach, to say the least, I'd say it is rather bad approach in most cases.
Here is some VBA code (not tested, though), here I used GetEntity() instead of AcadSelectionSet for single entity selewction. If it is possible to select more than one entity, you may look into SelectionSet with proper filters defined
{code}
Public Sub ChangeLine()
Dim ent As AcadEntity
Dim pt As Variant
Dim line As AcadLine
Dim eP(0 to 2) As Double
ThisDrawing.Utility.GetEntity ent, pt, "vbCr & "Please pick a line: "
''You need to write sone validation code to handle situation like when user hits "ESC" to cancel the pick, or picked blank space...
''Thus to make sure an AcadEntity is really picked.
''Then, make sure the picked entity is AcadLine (or whatever you expected), not something else
If TypeOf ent Is AcadLine Then
Set line=ent
''Do what ever you need to, such as change its end point:
eP(0)=20#:eP(1)=30#:eP(2)=0#
line.EndPoint=eP
line.Update
Else
MsgBox "Picked entity is not an AcadLine!"
End If
End Sub
{code}
You should be able translate to C# code for your exe app.
Again, it is bad idea to ask user switch from your exe app to AutoCAD to pick something. You make notice when your code run into the point when use is to pick, your exe app at this moment is the active window app, user has to first make the running AutoCAD active window app, then has to pick the Acad editor again to activate Acad's document window, then user can do the pick. After this, user may have to make your exe app active again in order to go back. This whole thing gives very awful user experience. Trying to use code to active different windows app (yours and AutoCAD) at needed moments may improve the user experience, but it is very difficult to do, considering your programming experience, or even not doable.
{code}
Public Sub ChangeLine()
Dim ent As AcadEntity
Dim pt As Variant
Dim line As AcadLine
Dim eP(0 to 2) As Double
ThisDrawing.Utility.GetEntity ent, pt, "vbCr & "Please pick a line: "
''You need to write sone validation code to handle situation like when user hits "ESC" to cancel the pick, or picked blank space...
''Thus to make sure an AcadEntity is really picked.
''Then, make sure the picked entity is AcadLine (or whatever you expected), not something else
If TypeOf ent Is AcadLine Then
Set line=ent
''Do what ever you need to, such as change its end point:
eP(0)=20#:eP(1)=30#:eP(2)=0#
line.EndPoint=eP
line.Update
Else
MsgBox "Picked entity is not an AcadLine!"
End If
End Sub
{code}
You should be able translate to C# code for your exe app.
Again, it is bad idea to ask user switch from your exe app to AutoCAD to pick something. You make notice when your code run into the point when use is to pick, your exe app at this moment is the active window app, user has to first make the running AutoCAD active window app, then has to pick the Acad editor again to activate Acad's document window, then user can do the pick. After this, user may have to make your exe app active again in order to go back. This whole thing gives very awful user experience. Trying to use code to active different windows app (yours and AutoCAD) at needed moments may improve the user experience, but it is very difficult to do, considering your programming experience, or even not doable.
Sorry,to a typo:
ThisDrawing.Utility.GetEntity ent, pt, "vbCr & "Please pick a line: "
Should be
ThisDrawing.Utility.GetEntity ent, pt, vbCr & "Please pick a line: "
ThisDrawing.Utility.GetEntity ent, pt, "vbCr & "Please pick a line: "
Should be
ThisDrawing.Utility.GetEntity ent, pt, vbCr & "Please pick a line: "
go here:
http://www.developerfusion.com/tools/convert/vb-to-csharp/
To clarify, are you building a .dll or an .exe?
http://www.developerfusion.com/tools/convert/vb-to-csharp/
To clarify, are you building a .dll or an .exe?
Dave O.
There are usually 2 ways to access data in a Excel spreadsheet file:
1. COM automating Excel application. You can find lots of example in Acad VBA NG or from the net. In this case, Excel must be installed. IMO, if the accessing is only for reading/writing data (i.e. you do not have to manipulating cell's format/look), this is not good option.
2. Using DAO/ADO directly read data from *.xls file without opening it in Excel application. In this case, Excel installation is not required. You can also find lots of example VB code from the net.
So, you need to understand, do you want to get data from *.xls file, or do you need to communicate with Excel application.
Not knowing what exactly your project is to do, it is difficult to have meaningful comment.
1. COM automating Excel application. You can find lots of example in Acad VBA NG or from the net. In this case, Excel must be installed. IMO, if the accessing is only for reading/writing data (i.e. you do not have to manipulating cell's format/look), this is not good option.
2. Using DAO/ADO directly read data from *.xls file without opening it in Excel application. In this case, Excel installation is not required. You can also find lots of example VB code from the net.
So, you need to understand, do you want to get data from *.xls file, or do you need to communicate with Excel application.
Not knowing what exactly your project is to do, it is difficult to have meaningful comment.
Googling "Read Excel With ADO" would bring you a lot of links. Here is one you can use directly:
http://support.microsoft.com/kb/257819
If you do want to go the Excel automating route, googling for "Automating Excel", here is one example:
http://www.eggheadcafe.com/tutorials/aspnet/8c6de397-f6d1-4696-919b-e50311dbd917/automating-excel.aspx
http://support.microsoft.com/kb/257819
If you do want to go the Excel automating route, googling for "Automating Excel", here is one example:
http://www.eggheadcafe.com/tutorials/aspnet/8c6de397-f6d1-4696-919b-e50311dbd917/automating-excel.aspx
