Time Picker Widget

It's a curious question and the answer may be good or bad depending on your perspective. "Why doesn't FileMaker have a time picker?". It has a calendar widget for working with date fields, why not time values?

The solution to the problem, as is often the case, can be managed by simply creating your own picker. In fact, if you don't like FileMaker's desktop based date picker you can create any variation you desire based on being able to create any style of layout you can imagine. While the same applies to a time picker, it may not be obvious how to implement if you've not worked with FileMaker for some extended amount of time.

In this video, I showcase a straight-forward time picker which works with both timestamp fields and time fields. It also includes some valuable utility scripts and concepts which can certainly be used in other areas of your FileMaker solutions. If you've ever come across the need for a time specific picker then adding this to your solution should save you a ton of time!

AttachmentSize
TimePickerWidget.zip1.61 MB

Comments

This is a great technique, I couldn't get the picker to open up underneath the field on my solution, than I realised if you move the technique file to a larger screen and extend the window so the window is larger, the picker disappears off screen or below the Filemaker window and that's the same issue I am experiencing. Any ideas how I can get the picker to appear under the field regardless of the screen size?
Thanks

Yes, one of the glitches I came across on my migration path. The key is to identify the window to which you want to attach the card. I forgot to name my field (with time data), so it didn't record the field name, and the card went to the default position. Had to close FMP to figure out the problem and fix it.

I'm guessing this doesn't work with version 17??

I just moved to FMP 17 and this is working for me as is. I did change the logic of up/down arrows, but other than that it transported to my system fine. A few glitches along the way due to operator error on order of migration!