Announcement

Collapse
No announcement yet.

TRACE and messaging

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • TRACE and messaging

    I haven't used TRACE much and noticed something. I have a main dialog and one child dialog. Both are modal with separate callbacks. My assumption was that whichever dialog was active would be the only one sending anything to its appropriate callback. What TRACE showed me was that's true for the main dialog, but when the child is active there are still occasional passes through the main callback. Is that normal?

    Thanks,
    Conrad

  • #2
    Well, your program is doing what your program does, and TRACE is doing what TRACE does.
    The particular item you mention may only be 'normal' to code that you write, or it may be normal to most code that is written.
    It may also be an indicator that this is where the problem, if there is one, with your code is, since it's doing something that you don't think should be happening.
    It would help to see the code or code that displays this behavior so someone can ascertain whether or not all is copacetic.
    TRACE ON traces until a TRACE OFF is encountered, so if TRACE bypasses a TRACE OFF it would indicate some kind of programmer error. You do not state whether this is the case, though.
    Rod
    I want not 'not', not Knot, not Knott, not Nott, not knot, not naught, not nought, but aught.

    Comment


    • #3
      It's perfectly normal and expected. There's lots of notifications sent all the time, it's just that you rarely need to worry about most of them.

      You want to see even more notifications to the inactive dialog? Drag the child dialog around, covering and uncovering areas of the parent.
      Michael Mattias
      Tal Systems (retired)
      Port Washington WI USA
      [email protected]
      http://www.talsystems.com

      Comment


      • #4
        Thanks, I just never appreciated how busy Windows is.

        CH

        Comment

        Working...
        X