The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Hide the close button
Posted: 25 Aug 06 10:59 AM
|
fiogf49gjkf0d When spawning forms, is there a way to hide the close button? Users need to strictly utilize the GUI. |
|
|
|
Re: Hide the close button
Posted: 28 Aug 06 12:57 AM
|
fiogf49gjkf0d I wont say it is impossible since there may be Win32 calls to do so (not my expertise). From within the SalesLogix toolbox, however, I would say this is not possible.
Please supply some more info on what you need and I am certain we can assist. For example, you can have code call your form and that code can react based on the modal result of that form. Using the X is the same as the user hitting cancel.
Timmus |
|
|
|
Re: Hide the close button
Posted: 28 Aug 06 7:49 AM
|
fiogf49gjkf0d Thanks for the info, Timmus. I had already put the necessary code in the form's "OnClose" event. I was just curious if it was possible to hide the button, which would just make things a little bit easier. |
|
|
| |
|
Re: Hide the close button
Posted: 28 Aug 06 1:50 PM
|
fiogf49gjkf0d Actually, with 6.2 and mainviews you can change the border style to resizable or a toolbox and it'll change the behavior of the window itself. There may be a style that turns it off but the total behavior may not be desired.
One thing you could do is to use the OnCloseQuery or OnClose events and specify a boolean that is set by "normal" close methods such as the Cancel or OK buttons. The routine can then tell if the user clicked X or not and even chastise them for doing so (OnCloseQuery). It's a lot of extra work when you place this in the context of EVERY form but it's probably better to use this on a couple of forms you know must be manipulated a certain way.
I totally understand why you'd want to do this. Users have a habit of clicking the X when they see the form is seemingly unresponsive. They then turn around not more than 2 seconds later and try again, causing the form to behave weirdly in certain instances because of caching. |
|
|
|