In my time as a developer I have had a few situations where the people asking me to write the software wanted to diable the close button for whatever reason. In all cases I managed to get them to rethink the idea by doing simple things by changing the workflow, putting extra thought into what is being done or saving temporary operation data. A lot of developers seem to forget about the end user just to make things easier for themselves. But in this situation it can end up a lot worse, because if the user feels really trapped when the window won't close then they can just end the process and that will definitely get the operation to end up in a very bad situation. I have a list of actions which would make me not use an application if a program does. Trying to stop the application from closing is actually on that list. So if this application, with the close disabling, came out onto the market then I wouldn't be using it. Christian Or you can just drag the you-want-to-reboot window to the bottom right and reboot when it suits you. As to why it wants to reboot, Raymond discussed that before: ‘Windows can but won't’ On the other hand, there was an article on Slashdot some time ago about one of those old systems (think twenty years ago or something), that could achieve close to 100% uptime and get security right. I thought I bookmarked it since it was interesting from a historical perspective, but I can't find it any more. I'd have to check but I'd think that the actual answer is slightly different from Shaka's: I suspect that SetClassLong would affect *all* windows of that class, even those already existing, and not just new ones. I don't care enough to write code to test this, but my reasoning is that the change is supposed to happen right then, so it would make sense for it to affect all windows, and this sentence from MSDN 'Calling SetClassLong with the GCL_WNDPROC index creates a subclass of the window class that affects all windows subsequently created with the class' implies that by specifically calling out GCL_WNDPROC 'affects all windows *subsequently* created' which implies that other values don't. May 19, 2011 - 2 min - Uploaded by David CouchPlease support me by clicking the AD. This short tutorial will show you how to use a. On the other hand, there was an article on Slashdot some time ago about one of those old systems (think twenty years ago or something), that could achieve close to 100% uptime and get security right. BeOS was close, if you're flexible in your definition of 'uptime.' You could, for example, kill, patch, and restart the networking subsystem without rebooting the kernel or anything else on the system. (Or any other subsystem on the machine.) But then again, if you have to kill networking, you're probably not going to count that as 'uptime' except as a technicality. The control includes the class for displaying cells with a user interface (UI) like a button. However, does not provide a way to disable the appearance of the button displayed by the cell. The following code example demonstrates how to customize the class to display buttons that can appear disabled. The example defines a new cell type, DataGridViewDisableButtonCell, that derives from. This cell type provides a new Enabled property that can be set to false to draw a disabled button in the cell. The example also defines a new column type, DataGridViewDisableButtonColumn, that displays DataGridViewDisableButtonCell objects. To demonstrate this new cell and column type, the current value of each in the parent determines whether the Enabled property of the DataGridViewDisableButtonCell in the same row is true or false.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |