[quote=190691:@Dave OBrien]Thanks Mike and Tim
I have already moved your 6 code folders in to a ‘CalTimeClass’ folder in my IDE - just keeps it neater for me.
Tim, I agree with you 100%, and since I ‘discovered’ the trick of hiding ( not closing ) the Chooser window so that I can still access the SelectedDate property, I have been able to revert back to the stock standard class as I downloaded it, with the exception of 2 items.
There are 2 places where, as far as I can see, the ‘virgin’ class requires changes after adding to the IDE.
These are the Cancel_Button Action, and the Finished_Button Action events. These need code so that the user can do whatever the user wants with them - great - but any code added by the user will break when an updated version of the class is downloaded and added to the IDE, replacing the existing modified class.
So if Mike is open to suggestions, may I please be so forward to request / suggest something along the lines of :
Add 2 properties to the class :
GoActive As Boolean = False
GoButtonSelected as Integer = 0
Modify the 2 existing buttons so that it is possible for users to use the chooser without having to make any changes in the class :
// for Finished_Button
GoButtonSelected = 1
GoActive = False
// for Cancel_Button
GoButtonSelected = 2
GoActive = False
This way, majority of the users can work with the class unchanged. The parent window where the instance is created can access the properties of the Chooser instance to get the :
GoActive ( set to true when opening the Chooser in the button action event, false = Chooser window has been closed )
GoButtonSelected ( 0 = Chooser window closed - no button clicked, 1 = Select Clicked, 2 = Cancel Clicked )
Just my 2c. Please ignore if a bad idea.[/quote]
Really anything at this level of the “DateTimeWindow” is open for you to do as much or as little with on a case by case need. My interest isn’t customizing a front end for all to use, but to provide the layer to do this with at your leisure.