Revit API. Work with the form in VS.

[andron_kozmos]

Good afternoon!

created a class- SortLevels

public class SortLevels : IExternalCommand
    {
       
        public bool IsTemplate { get; private set; }

        public Result Execute(ExternalCommandData commandData, ref string message, ElementSet elements)
        {
           
            UIDocument uiDoc = commandData.Application.ActiveUIDocument;

            Document doc = uiDoc.Document;

            FilteredElementCollector collector = new FilteredElementCollector(doc);
            ICollection<Element> levels = collector.OfCategory(BuiltInCategory.OST_Views).Where(x => !(x as Autodesk.Revit.DB.View).IsTemplate 
            && (x as Autodesk.Revit.DB.View).ViewType != ViewType.Elevation
            && (x as Autodesk.Revit.DB.View).ViewType != ViewType.ThreeD
            && (x as Autodesk.Revit.DB.View).ViewType != ViewType.Section).ToList();

as an example, displays the following kinds of levels.

Can you tell me, how to get the class into the form? How can this collector be inferred in the form in  checkedListBox1

private void checkedListBox1_SelectedIndexChanged_1(object sender, EventArgs e)
        {

            



        }

[RPTHOMAS108]

This is non-api knowledge best available elsewhere.

To start with you should create your own cut down class version of View containing: Id, Name and IsChecked.

You then need to put that into a collection object and bind the control to it (this is easier to do in WPF than Forms).

You are using a Forms CheckedListBox which is notoriously awkward in not allowing a binding to the check status of the individual item. Instead you could more easily use a WPF ListBox with a DataTemplate that has a CheckBox with CheckBox.IsChecked bound to IsChecked and CheckBox.Content bound to Name.

I would make it completely abstract since we are basically creating a checked listbox which could be used for any object not just Views

That is: if you create an interface with members 'Name' and 'IsChecked' then your class that you create to represent the view could implement that interface. Your dialogue could then just deal with the interface not caring at all what the object is. Selecting Views, Levels, Categories, Doughnuts (all the same).

[andron_kozmos]

Сan i see a sample code somewhere? I'm a beginner so it's hard for me to accept.