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. WPF
  4. DataGrid Event Not Firing

DataGrid Event Not Firing

Scheduled Pinned Locked Moved WPF
wpfwcfcomcollaborationhelp
3 Posts 2 Posters 8 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.
  • K Offline
    K Offline
    Kevin Marois
    wrote on last edited by
    #1

    I have a sample app with a AddingNewItem command for a DataGrid, but I can't get it to fire.

    There are no binding errors or other problems. It just doesn't fire. The Setter for the command do fire. My sample project is here [^] . Does anyone see what's wrong?

    In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.

    A 1 Reply Last reply
    0
    • K Kevin Marois

      I have a sample app with a AddingNewItem command for a DataGrid, but I can't get it to fire.

      There are no binding errors or other problems. It just doesn't fire. The Setter for the command do fire. My sample project is here [^] . Does anyone see what's wrong?

      In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.

      A Offline
      A Offline
      Andre Oosthuizen
      wrote on last edited by
      #2

      Without seeing the full XAML and ViewModel code, it's a bit challenging to figure out where your problem lies. More info is required to try and find a solution, no, we will not be opening your entire project to try and find a solution.

      K 1 Reply Last reply
      0
      • A Andre Oosthuizen

        Without seeing the full XAML and ViewModel code, it's a bit challenging to figure out where your problem lies. More info is required to try and find a solution, no, we will not be opening your entire project to try and find a solution.

        K Offline
        K Offline
        Kevin Marois
        wrote on last edited by
        #3

        Andre Oosthuizen wrote:

        no, we will not be opening your entire project to try and find a solution.

        Plenty of others have.

        In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.

        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