Bug Report T318608

Visible to All Users

DocumentViewer - DocumentViewer's Cursor property has no effect

jnm2

created 9 years ago (modified 9 years ago)

DocumentViewer.Cursor seems to have no effect. We need to set the default cursor to Default and AppStarting cursors at certain times, but if the document viewer shows the link cursor or any non-default cursor we do not want to override that. How can we hook into the calculation that determines which cursor is shown?

Answers approved by DevExpress Support

DevExpress Support Team

created 9 years ago

We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.

Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.

v15.2.4Download Official Update
v15.1.9Download Official Update

DevExpress Support Team

created 9 years ago (modified 9 years ago)

Hello Joseph,
It's possible to change the default cursor to a custom one when a user hovers a specific report control. In the XRControl.PreviewMouseMove event handler, provide a custom cursor for the preview control by using the Control.Cursor property. For instance:

C#
private void xrLabel_PreviewMouseMove(object sender, PreviewMouseEventArgs e) {  
            e.PreviewControl.Cursor = Cursors.Help;  
}

The result will be as follows: see the video.

If your scenario is different, please clarify it.

[Posted by Joseph N. Musser II]
This is what I got. Works well as far as I can tell. https://gist.github.com/jnm2/d9ca8b862ba4e55d9ec2
It would be nice if this was the behavior by default so people don't have to use the subclass.

Show previous comments (9)

jnm2 9 years ago

We're not interested in individual report controls. The entire DocumentViewer control should have the AppStarting cursor instead of the default cursor. This behavior is definitely not one we want in our report scripts! The behavior is just for the DocumentViewer control in one form in our application.

DevExpress Support Team 9 years ago

Okay Joseph,
DocumentViewer provides the BrickMouseMove event which occurs when the mouse pointer is moved over document bricks' region within PrintControl.

Please try this event and let me know whether or not this works for you.

jnm2 9 years ago

Okay! How do I use that to override the cursor?

DevExpress Support Team 9 years ago

Just cast a sender object to the Control type and then specify the cursor by using the Control.Cursor property.

DevExpress Support Team 9 years ago

Please note that this event also provides an argument of type BrickEventArgs containing data related to this event. You can use this data to determine the area that is mouse pointer is currently on.

jnm2 9 years ago

It works but it has a major shortcoming: the default cursor is still getting set first. Even though I'm setting the cursor (second) to AppStarting, there's enouch of a delay that the cursor bounces back and forth between the cursors as you move it across the control. Also, the AppStarting animation is constantly resetting. It looks ugly. How can I override the cursor before it gets set in the first place?

jnm2 9 years ago

Overriding DocumentViewerBase.TryGetCursor seems to work. Here's the behavior that *should* be the default:
       protected override bool TryGetCursor(IPage page, ref Cursor value)
       {
           base.TryGetCursor(page, ref value);
           if (value == null) value = Cursor;
           return true;
       }
I'm just missing the part that resets the cursor to Default when the document is first set and begins creating. That needs to be overridden too.

jnm2 9 years ago

Looks like DocumentViewerBase.ps_BeforeBuildPages is the culprit. It's hardcoded to set the cursor to Cursors.Default instead of to DocumentViewerBase.Cursor.

jnm2 9 years ago

This is what I got. Works well as far as I can tell. https://gist.github.com/jnm2/d9ca8b862ba4e55d9ec2
It would be nice if this was the behavior by default so people don't have to use the subclass.

DevExpress Support Team 9 years ago

Hello Joseph,
We appreciate your research. I am happy to hear that you've found the solution. FYI: I've informed our developers that the DocumentViewer's Cursor property value is not taken into account so they can research this behavior. Thank you for pointing this out.

jnm2 9 years ago

Thank you Jannet! You have no idea how much it means to me that DevExpress takes these things seriously.

DevExpress Support Team 9 years ago

You are always welcome, Joseph.

Created: November 30, 2015 4:22 PM

Modified: December 2, 2015 3:50 PM

Platform: WinForms

Product: XtraPrinting Library

Build: 15.1.8

Reproduced: True

Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

DocumentViewer - DocumentViewer's Cursor property has no effect

Answers approved by DevExpress Support

Recently viewed tickets