AR 9 and 11 designer draw control behaviour

AR 9 and 11 designer draw control behaviour

Posted by: ajanda on 1 August 2018, 7:43 am EST

• 

  ajanda

  • Post Options:
  • Link
    Copy

  Posted 1 August 2018, 7:43 am EST

  Hello

  We’ve noticed a strange behavior of Active Reports 9 and 11 designer. When adding new control by selecting it from toolbox and then “drawing” it on the designer control, if an event is fired right after drawing is finished (in this example MouseUp event) and in this event an action on some other designer is made (in this example - creating a new Designer) the application still in some way tries to continue drawing the control and the code doesn’t go forward till the mouse stops moving (please see recorded gif inside attached zip). Because how our application is build, this on our end can lead to some unexpected behavior and exceptions.
  
  We also noticed this was not an issue in earlier versions of Active Reports (eg AR6). Is there any way to fix this issue? I’m attaching sample application that can be used to reproduce this behavior (please note that this behavior is reproducible even without Thread.Sleep. It was just added to make debugging easier)

  attachment.zip

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 2 August 2018, 7:34 am EST

  Hello,

  Thanks for the information.

  I am able to replicate the problem at our end. I have escalated this to the development team(tracking id 261649) and will revert you back once have any information from them.

  Thanks
  
  Mohit

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 2 August 2018, 9:51 am EST

  Hello Adrian,

  Could you please specify your code requirement?

  Thanks

• 

  ajanda

  • Post Options:
  • Link
    Copy

  Posted 3 August 2018, 2:49 am EST

  Hello

  Unfortunately I’m familiar with ActiveReports library code but I’ll try to specify it the best I can:

  When user is drawing a control on Active Reports Designer, if an event is fired during drawing operation and said event operates on different instance of Active Reports Designer, user shouldn’t regain a control on the Designer, the Designer should stay locked from any input until drawing of the control is finished.

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 3 August 2018, 5:32 am EST

  Hello,

  Thanks for the information.

  However, could you please share the use case with us that you want to achieve. Also, could you please specify the list of event that you are using in your code.

  Thanks

• 

  ajanda

  • Post Options:
  • Link
    Copy

  Posted 6 August 2018, 3:37 am EST

  Hello

  Our application is a bit more complex than the sample I sent. Basically we are using external toolbox that communicates with AR Designer by changing Designer’s ToolBoxItem property. When that happens Designer’s ToolboxItemChanged event is fired. Then because we use our own controls that base on AR controls (they are basically AR SubReports with prepared in advance parameters) we create some temporary Designer in which we prepare the control so it’s not visible for user. Once the control is prepared on temporary Designer, we select it and ExecuteAction(DesignerAction.EditCut) on temporary one and ExecuteAction(DesignerAction.EditPaste) on visible one.

  So from AR library only ToolboxItemChanged event is used in this scenario.

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 7 August 2018, 6:33 am EST

  Hello,

  I have forwarded your issue to our developer team.

  Thanks,

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 17 August 2018, 9:13 am EST

  Hello,

  I have created the sample for you to achieve your requirement. Please refer to the attached sample.

  Thanks,
  
  C#.zip