Skip to main content

Grid Graphics

Comments

35 comments

  • Michael Sage

    Is there a phone number I can call you at. I'm still unclear about the process, it might be helpful to talk. Thanks.

    0
  • Dapfor Team

    btw, if NotifyPropertyChanged updates come from the GUI thread, then the Grid doesn't create ITask objects. The call stack will be as follows:

    GUI thread: YourObject.SomeProperty->FireNotification->IDataAccessor->Grid->Cell->Control.Invalidate(Rectangle)

    GUI thread (some time later): WM_PAINT->Grid drawing routine-> OnPaintRow() ->OnPaintCell() callback

    Best regards,

    Dapfor

     

     

     

     

    0
  • Dapfor Team

    Unfortunately we don't provide phone support.

    0
  • Michael Sage

    Ok, How often does the GUI thread service the queue of the IDispatcher, is it on a timer or does it dequeue as soon as an item is queued. Secondly, I am not very clear on why you said I wasn't right, Is it because I'm calling the Notify Events in the Dispatcher queue. Can you tell me what is wrong in my example code ? 

    0
  • Dapfor Team

    The GuiDispatcher posts a window message when the first Dispatch() method is called. The Windows distributes this message immediatly. When GuiDispatcher gets the message, its internal queue can contain several ITasks. What is about your example - it is fully correct. You call object's properties in the GUI thread via created tasks. The same effect you can get, if you set the dispatcher in the constructor of the grid. In this case the properties can be called in the non-GUI thread and the grid will synchronize threads itself via provided dispatcher. So we think the code will be more clean.

    Best regards,

    Dapfor

    0

Please sign in to leave a comment.

Powered by Zendesk