Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C#
  4. Using Collections of objects as public properties

Using Collections of objects as public properties

Scheduled Pinned Locked Moved C#
questiondesign
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L Offline
    L Offline
    Lost User
    wrote on last edited by
    #1

    Ive got a tab control im building from scratch. the control has a collection(ArrayList) of MyTab objects. How do i expose the collection so that in the properties of the control in design view, a user may add a MyTab object and set its properties? If i simply expose the collection publicly, the "Collection..." field shows up, but the 'add' button only adds a System.Class. I need the add button to display a MyTab object. you can see specifically what i want if you create an toolbar object on a form and click 'Buttons' in the properties section. when you add a new button, it shows up on the form and a 'toolbarbutton' object is created with properties you may edit. do i have to impliment my own collection class? thanks :confused:

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups