Event Colors
DayBackForFileMaker.EventColors History
Hide minor edits - Show changes to markup
https://www.seedcode.com/rootimages/stikipad/dayback/statuscolorssm.png
https://archive.seedcode.com/rootimages/stikipad/dayback/statuscolorssm.png
https://www.seedcode.com/rootimages/stikipad/dayback/assignstatussm.png
https://archive.seedcode.com/rootimages/stikipad/dayback/assignstatussm.png
Another option would be to add a second color to DayBack, and use that for the resource. You'll find a great example of this, along with the calc field and CSS required here: : https://www.seedcode.com/add-icons-colors…lemaker-calendar/
Another option would be to add a second color to DayBack, and use that for the resource. You'll find a great example of this, along with the calc field and CSS required here: : https://www.seedcode.com/add-icons-colors-Filemaker-calendar/
Another option would be to add a second color to DayBack, and use that for the resource. You'll find a great example of this, along with the calc field and CSS required here: : https://www.seedcode.com/add-icons-colors…lemaker-calendar/
Yes. A few different approaches are described here.
Yes. Version 10.16 introduced the ability to calculate event styles and add icons using CSS. Check it out: Event Styles. And a few different approaches are described here.
- And in the script "Load Calendar Settings - On Startup --- Edit Configuration Here ---" where line 92 specified the field you'll use when filtering by status. All three places should use the same field (though in the script here you can specify one field in each source).
- And in the script "Load Calendar Settings - On Startup --- Edit Configuration Here ---" where lines 100-106 specified the field you'll use when filtering by status (Look for the comment #Maps filters to fields). All three places should use the same field (though in the script here you can specify one field in each source).
In fact, these *are* a value list in that there's a "CalendarColors" table in DayBack where each of these status filters isa color. Adding and removing status filters here in the calendar is manipulating records in this "CalendarColors" table. The value list you use for status in your FileMaker layout should be based on the records in this table. That way you can assign statuses to events in your own layouts and in the calendar.
In fact, these *are* a value list in that there's a "CalendarColors" table in DayBack where each of these status filters is a color. Adding and removing status filters here in the calendar is manipulating records in this "CalendarColors" table. The value list you use for status in your FileMaker layout should be based on the records in this table. That way you can assign statuses to events in your own layouts and in the calendar.
Yes! As of build 9.72 of DayBack, you can assign a default color for each calendar source within the "Load Calendar Settings at Startup" script.
Yes! As of build 9.72 of DayBack, you can assign a default color for each calendar source within the "Load Source Settings at Startup --- Describe Your Sources Here ---" script.
Adjusting Status Colors
Adjusting Status Colors
!! Adjusting Status Colors
- And the value in your field is one of the values of the Status Filters shown on the "Filters" tab of the calendar/
- And in the script "Load Calendar Settings - On Startup --- Edit Configuration Here ---" where line 92 specified the field you'll use when filtering by status. All three places should use the same field (though in the script here you can specify one field in each source).
If you'd still like to set the source color as an option in the Status Filters list, you can create a new calc field in each source table set to "Source Name" of your source. Then follow the instructions in the video above for color-coding by a calculated field.
If you'd still like to set the source color as an option in the Status Filters list, you can create a new calc field in each source table set to "Source Name" of your source. Then follow the instructions in the video above to color-code by this calculation field instead of a status field.
Can I color code by Source instead of by a field?
Can I color code by calendar Source?
Setting up color coding begins in the "DBk_WebViewerSource" field you added to your events table when when integrating the calendar. The field you mapped to "status" there is the field DayBack looks at to color code your events. You'll also see a "color" field on the Source No X layout (Source No 1, Source No 2, etc.) you used . That layout has a tab called "colors" on which you can specify the field you'd like to use for color coding: this should be the same field you mapped to "status" in "DBk_WebViewerSource".
Setting up color coding begins in the "DBk_WebViewerSource" field you added to your events table when integrating the calendar. The field you mapped to "status" there is the field DayBack looks at to color code your events. You'll also see a "color" field on the Source No X layout (Source No 1, Source No 2, etc.) you used . That layout has a tab called "colors" on which you can specify the field you'd like to use for color coding: this should be the same field you mapped to "status" in "DBk_WebViewerSource".
Can I Based My Event Colors on a Calculated Field?
Can I Base My Event Colors on a Calculated Field?
Can I color events by Resource?
Sure thing. Although DayBack's Resource views help organize your events by resource, you may still want to set event colors based on the Resource assigned. Note that if you have multiple Resources selected, the event will be color-coded by the *first selected* Resource.
In the DBk_WebViewerSource field, map your Resource field to both sc_resource and sc_status. On the Source No _ layout, map the Resource field to both the resource and status placeholders. If you are using DayBack's built-in event popover, you will likely want to hide the "Status" item from appearing on the popover, since it will contain the same data as the Resource item. You can do this by modifying the $$sc_HidePopoverItems Set Variable step in the "Load Source Settings at Startup" script. Lastly, change/add entries in the Status Filters list on the calendar to assign a color for each of your Resources. That's it!
Yes. If you aren't using the "Status" field in your source table(s), change it to a calc field that returns the name of the source (e.g., "Sample Events"). Make sure the result type for the calc is Text.
If you are using the Status field, make a different calc field for the source. Then, map the field object on the "Colors" tab on the "Source No X" layouts to this new field, and also map the sc_status variable in the "DBk_WebViewerSource" calculation field to this new field. You'll also need need to edit the "Create Edit Delete Event..." script as described in the video above, so that the calendar does not attempt to write to this calculation field. Note that, if you are using DayBack's event popover instead of your own FileMaker layout, your original "Status" field will not be available on the event popover with this modification.
Yes! As of build 9.72 of DayBack, you can assign a default color for each calendar source within the "Load Calendar Settings at Startup" script.
If you'd still like to set the source color as an option in the Status Filters list, you can create a new calc field in each source table set to "Source Name" of your source. Then follow the instructions in the video above for color-coding by a calculated field.
Yes. If you aren't using the "Status" field in your source table(s), change it to a calc field that returns the name of the source (e.g., "Sample Events"). Make sure the result type for the calc is Text. If you are using the Status field, make a different calc field for the source, then just map the field object on the "Colors" tab on the "Source No X" layouts to that new field.
Yes. If you aren't using the "Status" field in your source table(s), change it to a calc field that returns the name of the source (e.g., "Sample Events"). Make sure the result type for the calc is Text.
If you are using the Status field, make a different calc field for the source. Then, map the field object on the "Colors" tab on the "Source No X" layouts to this new field, and also map the sc_status variable in the "DBk_WebViewerSource" calculation field to this new field. You'll also need need to edit the "Create Edit Delete Event..." script as described in the video above, so that the calendar does not attempt to write to this calculation field. Note that, if you are using DayBack's event popover instead of your own FileMaker layout, your original "Status" field will not be available on the event popover with this modification.
Can I add colored icons in addition to coloring the event?
Yes. A few different approaches are described here.
(:youtube h-hQsCWIOm8 width=500:)
(:youtube h-hQsCWIOm8 width=440:)
Can I Based My Event Colors on a Calculated Field?
Sure. You'll just want to change a couple changes to facilitate this. The following video shows what to do:
(:youtube h-hQsCWIOm8 width=500:)
- It needs to be mapped on the colors tab of the Source No X layout.You use that field in your colors calc: the field SampleEvents::DBk_ColorCalc.You've mapped your field to the label "status" in the field SampleEvents::DBk_WebViewerSourceAnd the value in your field is one of the values of the Status Filters shown on the "Filters" tab of the calendar/
In order for color coding to work, four things need to be true about the fields you've decided to base your color coding upon:
In order for color coding to work, four things need to be true about the fields you've decided to base your color coding upon:
The Details
Setting up color coding begins on the Source No X layout (Source No 1, Source No 2, etc.) you used when integrating the calendar. That layout has a tab called "colors" on which you can specify the field you'd like to use for color coding.
Setting up color coding begins in the "DBk_WebViewerSource" field you added to your events table when when integrating the calendar. The field you mapped to "status" there is the field DayBack looks at to color code your events. You'll also see a "color" field on the Source No X layout (Source No 1, Source No 2, etc.) you used . That layout has a tab called "colors" on which you can specify the field you'd like to use for color coding: this should be the same field you mapped to "status" in "DBk_WebViewerSource".
Here are some tips for creating and adjusting status colors.
Can I use the triangle of color from the Simple Day View on other views?
Yes. The simple day view (go to Settings / click "Use simple...") uses a different display for colors so that the color doesn't fill the whole event.
https://www.seedcode.com/rootimages/stikipad/pro12/trianglecolor.jpg
If you want to use this display on other views, edit the calc CalendarColorReptCalc in the calendar rows table. The second line of this calc sets "objecto" to use our triangle display only when the mode is "Day" (our simple day mode). Edit this line to use the triangle in any other modes you'd like. For your reference, a list of possible modes can be found here.
You may also want to change the font size of the value "display" at the end of this calc just on the week and month views if you switch them to the triangle display. You'll see an example line there commented out which does this for you.
(Note that colors were fundamentally reworked in version 7.23 and are much more stable now as they don't depend on fonts, check out the version history notes for instructions on upgrading to the new build.)
https://www.seedcode.com/rootimages/stikipad/dayback/assignstatuslg.png
https://www.seedcode.com/rootimages/stikipad/dayback/assignstatussm.png
https://www.seedcode.com/rootimages/stikipad/dayback/statuscolorssm.png
https://www.seedcode.com/rootimages/stikipad/dayback/statuscolorssm.png
https://www.seedcode.com/rootimages/stikipad/dayback/statuscolorssm.png
https://www.seedcode.com/rootimages/stikipad/dayback/statuscolorssm.png
A few notes about how this works...
https://www.seedcode.com/rootimages/stikipad/dayback/assignstatuslg.png
Adjusting Status Colors
In fact, these *are* a value list in that there's a "CalendaeColors" table in DayBack where each of these status filters isa color. Adding and removing status filters here in the calendar is manipulating records in this "CalendaeColors" table.
In fact, these *are* a value list in that there's a "CalendarColors" table in DayBack where each of these status filters isa color. Adding and removing status filters here in the calendar is manipulating records in this "CalendarColors" table. The value list you use for status in your FileMaker layout should be based on the records in this table. That way you can assign statuses to events in your own layouts and in the calendar.
https://www.seedcode.com/rootimages/stikipad/dayback/statuscolorssm.png
https://www.seedcode.com/rootimages/stikipad/dayback/statuscolorssm.png
Note that there's also a color field in the events table so we can show a color beside the event on the Event List and Event Details layouts. This calc (SampleEvents::DBk_ColorCalc) begins with a Let() statement were you can specify which field is being used for your colors.
The calendar colors events based on the contents of a field of your choosing. We call this field the event "status" in the documentation and sample file, but you can use any field you'd like.
Setting up color coding begins on the Source No X layout (Source No 1, Source No 2, etc.) you made when integrating the calendar. That layout has a tab called "colors" on which you can specify the field you'd like to use for color coding.
Then, on the Settings tab of the calendar you'll see a button called "assign colors". Click that and you can drag a color into each one of your "status" values.
https://www.seedcode.com/rootimages/stikipad/pro12/assigncolors.png
A few notes about how this works...
The calendar colors events based on the contents of a field of your choosing. We call this field the event "status" in the documentation and sample file, but you can use any field you'd like and translate the interface to call it something else: "department", "category", "state".
We do suggest using this for something temporal about the event (like its confirmation status) and use resources for more concrete facts about the event like where it is or whose it is.
Setting up color coding begins on the Source No X layout (Source No 1, Source No 2, etc.) you used when integrating the calendar. That layout has a tab called "colors" on which you can specify the field you'd like to use for color coding.
Then, on the Filters tab of the calendar you'll see a list of the calendar's "statuses". These should be the possible values of the field you mapped to status: think of these like a value list for that field.
In fact, these *are* a value list in that there's a "CalendaeColors" table in DayBack where each of these status filters isa color. Adding and removing status filters here in the calendar is manipulating records in this "CalendaeColors" table.
https://www.seedcode.com/rootimages/stikipad/dayback/statuscolorssm.png
A few notes about how this works...
(Note that colors were fundamentally reworked in version 7.23 and are much more stable now as they don't depend on fonts, check out the version history notes for instructions on upgrading to the new build.)
Yes. Toward the end of the "Load Calendar Settings - On Startup..." script, set the $$sc_ColorCodeBySource variable to "1". Then change the values entered on the "Assign Colors" layout to match the names of your sources. Use the source names exactly as they are being set into the $$sc_SourceName[X] variable in the "Load Source Settings at Startup --- Describe Your Sources Here" script (e.g., "Sample Events").
Yes. If you aren't using the "Status" field in your source table(s), change it to a calc field that returns the name of the source (e.g., "Sample Events"). Make sure the result type for the calc is Text. If you are using the Status field, make a different calc field for the source, then just map the field object on the "Colors" tab on the "Source No X" layouts to that new field.
Yes. Toward the end of the "Load Calendar Settings - On Startup..." script, set the $$sc_ColorCodeBySource variable to "1". Then change the values entered on the "Assign Colors" layout to match the names of your sources. Use the source names that are being set into the $$sc_SourceName[X] variable in the "Load Source Settings at Startup --- Describe Your Sources Here" script (e.g., "Sample Events").
Yes. Toward the end of the "Load Calendar Settings - On Startup..." script, set the $$sc_ColorCodeBySource variable to "1". Then change the values entered on the "Assign Colors" layout to match the names of your sources. Use the source names exactly as they are being set into the $$sc_SourceName[X] variable in the "Load Source Settings at Startup --- Describe Your Sources Here" script (e.g., "Sample Events").
Yes. Toward the end of the script "Load Calendar Settings - On Startup..." you'll see a setting for this: set that to "1". Then change the names entered for the "statuses" in the screen above to be the names of your sources. Use the same names you're using on the first tab on your Source No X layout.
Yes. Toward the end of the "Load Calendar Settings - On Startup..." script, set the $$sc_ColorCodeBySource variable to "1". Then change the values entered on the "Assign Colors" layout to match the names of your sources. Use the source names that are being set into the $$sc_SourceName[X] variable in the "Load Source Settings at Startup --- Describe Your Sources Here" script (e.g., "Sample Events").