changing Mouse cursor

[bpereira]

I am using slickedit 13.0.0.0 and in some forms the mouse arrow is modified, this is quite annoying when you don't use the default windows cursor, is there a way to fix this ?

[chrisant]

In Slick-C, each control on a form can be set to use a particular mouse cursor (at least on Windows it can, which directly exposes Windows' native support for that).  It sounds like some controls on some forms are explicitly using a particular cursor.

If they are forms from your own macros or third party macros, you can fix them by opening the form (Macro->Open Form) and clicking on the offending controls and changing the Mouse Pointer property, Save Form.

If they are standard SlickEdit forms, you can still do the above to adjust them, but please report the controls that you adjust to support@slickedit.com so they can be fixed in a future release (otherwise for example you'll have to re-fix again them when you upgrade).

Also note that if you reload a macro source module that defines a form, that will reset the form back to its original definition.  So you might want to track down the source files that define the forms you modify, and adjust their sources to specify an appropriate mouse pointer (which probably amounts to deleting a line that was explicitly specifying an undesirable mouse pointer).

[bpereira]

I have not made any macro, just installed the slickedit my company bought.

If I well understand what you are saying, I should fix myself slickedit component ? I find this a bit rude since we paid quite a lot of money for the editor. So at leas could you point me out where is the Left panel (Project, Defs, Class, ...) thing so I can modify it ?

[chrisant]

I'm a customer, like you.  I'm not saying you "should" fix it, I'm saying that if it's important to you to get a fix as soon as possible, then you "can" fix it yourself, if you want to.  I suppose you can think of it as rude that there is a cosmetic bug in the product, but I think it's great that in SlickEdit it is possible to fix stuff like this on your own, if you need a fix sooner than the company is able to provide one.  There aren't many products where you can fix them yourself if you really need to.  It is good for mouse cursors to look right, but it's not the kind of thing I would get very excited about.

Perhaps the best thing for you to do, is to write an email to support@slickedit.com and tell them which controls, on which forms, have the wrong cursors.  The more specific and detailed you can be, the more likely they can find them quickly and fix them.

[bpereira]

Thx for your help, I would have loved to hear some offical support on this subject, I cant believe I am the only slickedit user that have a non default windows cursor. (Or am I ??) 

[chrisant]

To get official support, you should contact support@slickedit.com.  These are the Community Forums where customers interact with each other.  Sometimes the SlickEdit folks drop in here, too, but for official support you should contact the official support:  support@slickedit.com.

[ScottW, VP of Dev]

@bpereira: We have confirmed this bug  Yes, you may actually be the first to report this. Many of the team have been here for more than 10 years and no one recalls this being reported previously.    I'm not sure when we'll be able to fix that, but it has been noted.

As noted by chrisant, these are our Customer Forums where customers can interact and get help from one another. We make an effort to review posts and answer a great many, but there are times when we don't get to respond to as many as we'd like. Formal support is provided using the email address provided by chrisant or by calling us via the telephone. Even if you don't have a Maintenance & Support agreement you can drop us a line and report a bug.

If you are new here, the suggestion to fix this problem yourself may seem a bit odd. Some of our long-time users have developed a remarkable facility with Slick-C and our APIs. These are the same ones we use for our own development. So, you'll find a number of bug fixes posted here before we have a chance to release a fix ourselves.

[Clark]

Easy fix.  The 13.0.1 update will have this fix.