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. DataGrid control

DataGrid control

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

    How i can fire(run) an event on a DataGrid cell?

    D 1 Reply Last reply
    0
    • S sasan56

      How i can fire(run) an event on a DataGrid cell?

      D Offline
      D Offline
      DougW48
      wrote on last edited by
      #2

      It depends on the type of cell...if it's just a normal text box, then you can handle the event on the textbox itself...

      D 1 Reply Last reply
      0
      • D DougW48

        It depends on the type of cell...if it's just a normal text box, then you can handle the event on the textbox itself...

        D Offline
        D Offline
        drayab
        wrote on last edited by
        #3

        How do you get the CurrentCell's text box from the data grid? Greg Bayard

        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