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. forms

forms

Scheduled Pinned Locked Moved C#
question
2 Posts 2 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.
  • X Offline
    X Offline
    xilefxilef
    wrote on last edited by
    #1

    Hi I have a mainform that opens up another form 'A'. By doing something on form 'A', opens up form 'B'. Both forms 'A' and 'B' should have access to the instance and fields of the mainform. What is the best approach? This is not MDI. Should it be? Can MDI be avoided in this case?

    H 1 Reply Last reply
    0
    • X xilefxilef

      Hi I have a mainform that opens up another form 'A'. By doing something on form 'A', opens up form 'B'. Both forms 'A' and 'B' should have access to the instance and fields of the mainform. What is the best approach? This is not MDI. Should it be? Can MDI be avoided in this case?

      H Offline
      H Offline
      Heath Stewart
      wrote on last edited by
      #2

      One way is to have each opening form pass an instance of itself to the form it opens and have that new form store that instance. If you want to access you form class's methods and properties, define the field in the new form as the type of your form and not simply Form (otherwise you'll have to cast your field to the right type before calling non-overridden methods and properties). Such a property does already exist and allows owned forms to be minimized and restored along with the owning form. Read the documentation[^] for the Form.Owner property for more information. This posting is provided "AS IS" with no warranties, and confers no rights. Software Design Engineer Developer Division Customer Product-lifecycle Experience Microsoft [My Articles] [My Blog]

      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