Event Colors
DayBackOnline.EventColors History
Hide minor edits - Show changes to output
Changed lines 41-43 from:
Yes. In Admin / Sources / Source Settings you'll see a setting for the default event color for that source: enter your color there (in RGB format) and the pull the status field from your event popover.
''Pulling or removing popover fields isn'tenabled in the DayBack beta yet but it's coming.''
''Pulling or removing popover fields isn't
to:
Yes. In Admin / Sources / Source Settings you'll see a setting for the default event color for that source: enter your color there (in RGB format) and the pull the status field from your event popover but unchecking "enabled".
Changed lines 11-14 from:
When the value of that field matches on of the values in DayBack's list of status
Then, on the Filters tab of the calendar you'll see athe 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.
Then, on the Filters tab of the calendar you'll see a
to:
When the value of that field matches on of the values in DayBack's list of status filters then you'll see colors in your event.
You'll maintain the list of statuses and their colors on the filters tab of the DayBack: think of these like a value list for that field.
You'll maintain the list of statuses and their colors on the filters tab of the DayBack: think of these like a value list for that field.
Changed lines 17-18 from:
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.
to:
In DayBack for FilleMaker these values come from a value list in your file, but in DayBack Online these values not taken from your file but are part of your group's DayBack account so you'll create and maintain this list in DayBack Online, not in FileMaker.
This is the same list you'll see in the event details popover:
This is the same list you'll see in the event details popover:
Changed lines 27-28 from:
-> Click the "+" button above the list of status filters to make a new one (and a new record in the "CalendarColors" table.) Your cursor will be in the name field.
to:
-> Click the "+" button above the list of status filters to make a new one: your cursor will be in the name field.
Changed lines 37-40 from:
%center% (:youtube h-hQsCWIOm8 width
to:
No. The status/color field needs to be editable. You can, however, use an auto-enter calc here. =)
Changed lines 41-42 from:
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.
to:
Yes. In Admin / Sources / Source Settings you'll see a setting for the default event color for that source: enter your color there (in RGB format) and the pull the status field from your event popover.
''Pulling or removing popover fields isn't enabled in the DayBack beta yet but it's coming.''
''Pulling or removing popover fields isn't enabled in the DayBack beta yet but it's coming.''
Changed lines 47-65 from:
!! Troubleshooting Colors
Here are some tips to make sure color coding works as you expect.
-> '''1.''' Make sure that the field you use for color mapping on the Source No X layout, and the field you use in SampleEvents::DBk_ColorCalc are the same fields. 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:
--> 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_WebViewerSource
--> And the value in your field is one of the values of the Status Filters shown on the "Filters" tab of the calendar/
-> '''2.''' Make sure the values in the field you've mapped to color is a value in the list of Status Filters in the calendars sidebar.
-> '''3.''' Finally make sure the any value lists of possible statuses (or whatever value list you're using as possible values for ''your'' color coded field) matches the list of values shown in DayBack: the best way to do this is to base any value list on the name field in the "CalendarColors" table. This way if you assign a "status" outside the calendar you'll be using the same values as inside the calendar
to:
Sadly, no. Only local fields are supported.
Changed lines 3-4 from:
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 [[translation | translate]] the interface to call it something else: "department", "category", "state".
to:
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 field mapping, but you can use any field you'd like and [[translation | translate]] the interface to call it something else: "department", "category", "state".
Changed lines 9-11 from:
Setting up color coding begins in the "DBk_WebViewerSource" field you added to your events table when when [[integration | 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".
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.
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.
to:
Setting up color coding begins in [[field mapping]] where you're asked which field DayBack should us for "status" (should use for color coding).
When the value of that field matches on of the values in DayBack's list of status
When the value of that field matches on of the values in DayBack's list of status
Changed line 37 from:
(:youtube h-hQsCWIOm8 width=500:)
to:
%center% (:youtube h-hQsCWIOm8 width=440:)
Added lines 32-37:
!! 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:)
Changed lines 47-53 from:
-> 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_WebViewerSource
-> And the value in your field is one of the values of the Status Filters shown on the "Filters" tab of the calendar/
-> 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_WebViewerSource
-> And the value in your field is one of the values of the Status Filters shown on the "Filters" tab of the calendar/
to:
--> 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_WebViewerSource
--> And the value in your field is one of the values of the Status Filters shown on the "Filters" tab of the calendar/
--> 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_WebViewerSource
--> And the value in your field is one of the values of the Status Filters shown on the "Filters" tab of the calendar/
Deleted lines 6-15:
-> 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_WebViewerSource
-> And the value in your field is one of the values of the Status Filters shown on the "Filters" tab of the calendar/
Changed lines 45-53 from:
-> '''1.''' Make sure that the field you use for color mapping on the Source No X layout, and the field you use in SampleEvents::DBk_ColorCalc are the same fields.
to:
-> '''1.''' Make sure that the field you use for color mapping on the Source No X layout, and the field you use in SampleEvents::DBk_ColorCalc are the same fields. 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:
-> 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_WebViewerSource
-> And the value in your field is one of the values of the Status Filters shown on the "Filters" tab of the calendar/
-> 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_WebViewerSource
-> And the value in your field is one of the values of the Status Filters shown on the "Filters" tab of the calendar/
Added lines 6-17:
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:
-> 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_WebViewerSource
-> And the value in your field is one of the values of the Status Filters shown on the "Filters" tab of the calendar/
!! The Details
Changed line 7 from:
Setting up color coding begins on the Source No X layout (Source No 1, Source No 2, etc.) you used when [[integration | 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.
to:
Setting up color coding begins in the "DBk_WebViewerSource" field you added to your events table when when [[integration | 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".
Changed lines 21-24 from:
->
to:
Here are some tips for creating and adjusting status colors.
-> Click the "+" button above the list of status filters to make a new one (and a new record in the "CalendarColors" table.) Your cursor will be in the name field.
-> Select the color you'd like by manipulating the color picker. It consists of three columns. The left, and widest, lets you fine-tune the color. The middle column lets you pick the general color spectrum, and the third column adjusts the transparency.
-> Click the "+" button above the list of status filters to make a new one (and a new record in the "CalendarColors" table.) Your cursor will be in the name field.
-> Select the color you'd like by manipulating the color picker. It consists of three columns. The left, and widest, lets you fine-tune the color. The middle column lets you pick the general color spectrum, and the third column adjusts the transparency.
Changed lines 29-30 from:
-> You can easily alter the pallets of possible colors by editing the field definition for the field "CalendarInterface::ColorRGBValues" where the RGB values of each pallet are declared.
to:
-> Click on the gear icon beside an existing color to edit or delete it. Note that deleting or renaming a color here doesn't change the value of that field in any events that may be using that status/color.
Deleted lines 38-47:
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.
%center% %width=440px% 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 [[ModesInTheCalendar | 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.
Changed lines 43-55 from:
->
->
->
-> '''4.''' Still not working? Try running the script "Load Calendar Graphics - alternate".
-> '''5.''' Finally make sure the value list of possible statuses (or whatever value list you're using as possible values for ''your'' color coded field) matches the list of values shown in the Assign Colors layout.
-> '''6.''' If you see a black bar instead of your color, it is likely that you have operators (math symbols or FileMaker expressions) in the color name (the event status). We try to trap for most of these but there are a lot of possible combinations. Try different versions of your status name without the operators. Remember you need to change this in the event itself, in the status value list, and in the "assign colors" screen in settings
to:
-> '''1.''' Make sure that the field you use for color mapping on the Source No X layout, and the field you use in SampleEvents::DBk_ColorCalc are the same fields.
-> '''2.''' Make sure the values in the field you've mapped to color is a value in the list of Status Filters in the calendars sidebar.
-> '''3.''' Finally make sure the any value lists of possible statuses (or whatever value list you're using as possible values for ''your'' color coded field) matches the list of values shown in DayBack: the best way to do this is to base any value list on the name field in the "CalendarColors" table. This way if you assign a "status" outside the calendar you'll be using the same values as inside the calendar.
-> '''2.''' Make sure the values in the field you've mapped to color is a value in the list of Status Filters in the calendars sidebar.
-> '''3.''' Finally make sure the any value lists of possible statuses (or whatever value list you're using as possible values for ''your'' color coded field) matches the list of values shown in DayBack: the best way to do this is to base any value list on the name field in the "CalendarColors" table. This way if you assign a "status" outside the calendar you'll be using the same values as inside the calendar.
Changed line 17 from:
%center% %newwin width=440px% [[https://www.seedcode.com/rootimages/stikipad/dayback/assignstatussm.png | https://www.seedcode.com/rootimages/stikipad/dayback/assignstatuslg.png]]
to:
%center% %newwin width=440px% [[https://www.seedcode.com/rootimages/stikipad/dayback/assignstatuslg.png | https://www.seedcode.com/rootimages/stikipad/dayback/assignstatussm.png]]
Changed line 13 from:
%center% %newwin width=440px% [[https://www.seedcode.com/rootimages/stikipad/dayback/statuscolorssm.png | https://www.seedcode.com/rootimages/stikipad/dayback/statuscolorssm.png]]
to:
%center% %newwin width=440px% [[https://www.seedcode.com/rootimages/stikipad/dayback/statuscolorslg.png | https://www.seedcode.com/rootimages/stikipad/dayback/statuscolorssm.png]]
Added lines 13-14:
%center% %newwin width=440px% [[https://www.seedcode.com/rootimages/stikipad/dayback/statuscolorssm.png | https://www.seedcode.com/rootimages/stikipad/dayback/statuscolorssm.png]]
Changed lines 17-20 from:
%center% %newwin width=440px% [[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...'''
to:
%center% %newwin width=440px% [[https://www.seedcode.com/rootimages/stikipad/dayback/assignstatussm.png | https://www.seedcode.com/rootimages/stikipad/dayback/assignstatuslg.png]]
!! Adjusting Status Colors
!! Adjusting Status Colors
Changed line 25 from:
-> You can '''override the color''' of any status by simply typing a new RGB value into each row.
to:
-> If you have colors you'd like to match exactly, simply type the RGBA value in right below the color picker. (The "A" in RGBA is alpha, or transparency, so just enter 1 if you're trying to match colors exactly.)
Changed line 13 from:
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.
to:
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.
Changed line 15 from:
%center% %newwin width=500px% [[https://www.seedcode.com/rootimages/stikipad/dayback/statuscolorssm.png | https://www.seedcode.com/rootimages/stikipad/dayback/statuscolorssm.png]]
to:
%center% %newwin width=440px% [[https://www.seedcode.com/rootimages/stikipad/dayback/statuscolorssm.png | https://www.seedcode.com/rootimages/stikipad/dayback/statuscolorssm.png]]
Changed line 9 from:
to:
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.
Changed lines 3-14 from:
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 [[integration | 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.
-> (Note: We also have 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::z_sc_ColorCalc) begins with a Let() statement were you can specify which field is being used for your colors)
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.
%center% %width=500px% https//www.seedcode.com/rootimages/stikipad/pro12/assigncolors.png
A few notes about how this works...
Setting up color coding begins on the Source No X layout (Source No 1, Source No 2, etc.) you made when [[integration | integrating]]
-> (Note: We also have 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::z_sc_ColorCalc) begins with a Let() statement were you can specify which field is being used for your colors
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
%center% %width=500px% https
A few notes about how this works
to:
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 [[translation | 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 [[integration | 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.
-> (Note: We also have 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.)
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.
%center% %newwin width=500px% [[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...'''
''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 [[integration | 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.
-> (Note: We also have 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.)
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.
%center% %newwin width=500px% [[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...'''
Added lines 45-46:
(Note that colors were fundamentally reworked in [[version history | 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.)
Changed line 26 from:
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").
to:
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.
Changed line 26 from:
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").
to:
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").
Changed line 26 from:
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.
to:
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").
Changed line 56 from:
-> '''6.''' Older versions of the calendar can have a problem with operators in the color name (the event status). You can read up on this issue and check out some workarounds %newwin% [[https://www.seedcode.com/support/viewtopic.php?f=25&t=2897&p=7002 | here]].
to:
-> '''6.''' If you see a black bar instead of your color, it is likely that you have operators (math symbols or FileMaker expressions) in the color name (the event status). We try to trap for most of these but there are a lot of possible combinations. Try different versions of your status name without the operators. Remember you need to change this in the event itself, in the status value list, and in the "assign colors" screen in settings.
Changed lines 30-45 from:
Yes.
So this is kind of a big-picture thing. The calendar is designed to be easily integrated-- that is why we have field mapping layouts like "Source No 1" and get your color field from there. However, once you HAVE integrated the calendar, you can stop relying on some of our abstractions and hard-code some things. So if your source isn't going to change (you're not going to point the calendar at another table) you can get creative with this....
Edit the script "Write One FileMaker Event in iCal Format" and find the line where we set the variabel $scical_Status
That is the color line. In that calc, replace GetField ( $$sc_FieldForStatus ) with a look at your event's related project and grab that color if there is one. Remember, we're on the Source No 1 layout when this happens, so you'll need a valid relationship to projects from there, but assuming you have one, that calc could begin...
Let ( [
-> p = RelatedProject::Color ;
-> s = if ( isempty ( p ) ; GetField ( $$sc_FieldForStatus ) ; p )
] ;
Note that you'll have to make sure your colors match the possible values of a project's status on the Settings tab's "assign colors" screen.
So this is kind of
Edit the script "Write One FileMaker Event in iCal Format" and find the line where we set the variabel $scical_Status
That is the color line. In that calc, replace GetField ( $$sc_FieldForStatus ) with a look at your event's related project and grab that color if there is one. Remember, we're on the Source No 1 layout when this happens, so you'll need a valid relationship to projects from there, but assuming you have one, that calc could begin...
Let ( [
-> p = RelatedProject::Color ;
-> s = if ( isempty ( p ) ; GetField ( $$sc_FieldForStatus ) ; p )
] ;
Note that you'll have to make sure your colors match the possible values of a project's status on the Settings tab's "assign colors" screen
to:
Yes, but only if you create a calc in the events table that reflects this value from the related record (the project in this example). All the fields on the Source No X layout need to come from the table that layout is based on--not from related tables.
Changed lines 11-13 from:
%center% %width=500px% https://www.seedcode.com/rootimages/stikipad/nextcal/assigncolors.png
to:
%center% %width=500px% https://www.seedcode.com/rootimages/stikipad/pro12/assigncolors.png
Added lines 54-55:
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.
Changed lines 64-66 from:
-> '''4.''' Finally make sure the value list of possible statuses (or whatever value list you're using as possible values for ''your'' color coded field) matches the list of values shown in the Assign Colors layout.
->'''5.''' Older versions of the calendar can have a problem with operators in the color name (the event status). You can read up on this issue and check out some workarounds %newwin% [url=https://www.seedcode.com/support/viewtopic.php?f=25&t=2897&p=7002]here[/url].
->
to:
-> '''4.''' Still not working? Try running the script "Load Calendar Graphics - alternate".
-> '''5.''' Finally make sure the value list of possible statuses (or whatever value list you're using as possible values for ''your'' color coded field) matches the list of values shown in the Assign Colors layout.
-> '''6.''' Older versions of the calendar can have a problem with operators in the color name (the event status). You can read up on this issue and check out some workarounds %newwin% [[https://www.seedcode.com/support/viewtopic.php?f=25&t=2897&p=7002 | here]].
-> '''5.''' Finally make sure the value list of possible statuses (or whatever value list you're using as possible values for ''your'' color coded field) matches the list of values shown in the Assign Colors layout.
-> '''6.''' Older versions of the calendar can have a problem with operators in the color name (the event status). You can read up on this issue and check out some workarounds %newwin% [[https://www.seedcode.com/support/viewtopic.php?f=25&t=2897&p=7002 | here]].
Changed lines 50-51 from:
%center% %width=400px% https://www.seedcode.com/rootimages/stikipad/pro12/trianglecolor.jpg
to:
%center% %width=440px% https://www.seedcode.com/rootimages/stikipad/pro12/trianglecolor.jpg
Changed lines 50-51 from:
%center% %width=500px% https://www.seedcode.com/rootimages/stikipad/pro12/trianglecolor.jpg
to:
%center% %width=400px% https://www.seedcode.com/rootimages/stikipad/pro12/trianglecolor.jpg
Changed lines 50-51 from:
%center% https://www.seedcode.com/rootimages/stikipad/pro12/trianglecolor.jpg
to:
%center% %width=500px% https://www.seedcode.com/rootimages/stikipad/pro12/trianglecolor.jpg
Changed lines 48-49 from:
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. If you want to use this di
to:
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.
%center% 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 [[ModesInTheCalendar | here]].
%center% 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 [[ModesInTheCalendar | here]].
Added lines 46-49:
!! 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. If you want to use this di
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. If you want to use this di
Added lines 57-58:
-> '''5.''' Older versions of the calendar can have a problem with operators in the color name (the event status). You can read up on this issue and check out some workarounds %newwin% [url=https://www.seedcode.com/support/viewtopic.php?f=25&t=2897&p=7002]here[/url].
Changed lines 44-45 from:
to:
Note that you'll have to make sure your colors match the possible values of a project's status on the Settings tab's "assign colors" screen.
Changed lines 38-40 from:
to:
Let ( [
-> p = RelatedProject::Color ;
-> s = if ( isempty ( p ) ; GetField ( $$sc_FieldForStatus ) ; p )
-> p = RelatedProject::Color ;
-> s = if ( isempty ( p ) ; GetField ( $$sc_FieldForStatus ) ; p )
Changed lines 40-42 from:
s = if ( isempty ( p ) ; GetField ( $$sc_FieldForStatus ) ; p ) ] ;
to:
s = if ( isempty ( p ) ; GetField ( $$sc_FieldForStatus ) ; p )
] ;
] ;
Changed lines 40-43 from:
s = if ( isempty ( p ) ; GetField ( $$sc_FieldForStatus ) ; p )
-> ] ;
to:
s = if ( isempty ( p ) ; GetField ( $$sc_FieldForStatus ) ; p ) ] ;
Added lines 28-43:
!! Can I color by a field outside the Event, like the Event's Project's Status?
Yes.
So this is kind of a big-picture thing. The calendar is designed to be easily integrated-- that is why we have field mapping layouts like "Source No 1" and get your color field from there. However, once you HAVE integrated the calendar, you can stop relying on some of our abstractions and hard-code some things. So if your source isn't going to change (you're not going to point the calendar at another table) you can get creative with this....
Edit the script "Write One FileMaker Event in iCal Format" and find the line where we set the variabel $scical_Status
That is the color line. In that calc, replace GetField ( $$sc_FieldForStatus ) with a look at your event's related project and grab that color if there is one. Remember, we're on the Source No 1 layout when this happens, so you'll need a valid relationship to projects from there, but assuming you have one, that calc could begin...
-> Let ( [
p = RelatedProject::Color ;
s = if ( isempty ( p ) ; GetField ( $$sc_FieldForStatus ) ; p )
] ;
Yes.
So this is kind of a big-picture thing. The calendar is designed to be easily integrated-- that is why we have field mapping layouts like "Source No 1" and get your color field from there. However, once you HAVE integrated the calendar, you can stop relying on some of our abstractions and hard-code some things. So if your source isn't going to change (you're not going to point the calendar at another table) you can get creative with this....
Edit the script "Write One FileMaker Event in iCal Format" and find the line where we set the variabel $scical_Status
That is the color line. In that calc, replace GetField ( $$sc_FieldForStatus ) with a look at your event's related project and grab that color if there is one. Remember, we're on the Source No 1 layout when this happens, so you'll need a valid relationship to projects from there, but assuming you have one, that calc could begin...
-> Let ( [
p = RelatedProject::Color ;
s = if ( isempty ( p ) ; GetField ( $$sc_FieldForStatus ) ; p )
] ;
Changed lines 26-27 from:
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 name of 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.
to:
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.
Changed lines 26-27 from:
Yes. Toward the end of the script "Load Calendar Settings - On Startup..." you'll see a setting for this: set that to "1". Then, on each of your "Source No X" layouts, edit the assign color section so that it just contains the name of your source in the color you'd want to see. This source name must match the source name used on the fist tab of you "Source No X" layout.
to:
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 name of 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.
Changed lines 32-36 from:
-> Make sure that the field you use for color mapping on the Source No X layout, and the field you use in SampleEvents::z_sc_ColorCalc are the same fields.
-> If no events show up with colors navigate to the Calendar Rows layout in layout mode and make sure there is a big chunk of color in the field CalendarColorGlob. If there isn't, run the upon opening script again.If that doesn't get any color visible in that field (it should be visible in the field without you having to enter the field with your cursor), copy and paste the contents of that field from an uncloned copy of the file.
-> Finally make sure the value list of possible statuses (or whatever value list you're using as possible values for ''your'' color coded field) matches the list of values shown in the Assign Colors layout.
-> If no events show up with colors navigate to the Calendar Rows layout in layout mode and make sure there is a big chunk of color in the field CalendarColorGlob. If there isn't, run the upon opening script again.
-> Finally make sure the value list of possible statuses (or whatever value list you're using as possible values for ''your'' color coded field) matches the list of values shown in the Assign Colors layout.
to:
-> '''1.''' Make sure that the field you use for color mapping on the Source No X layout, and the field you use in SampleEvents::z_sc_ColorCalc are the same fields.
-> '''2.''' If no events show up with colors navigate to the Calendar Rows layout in layout mode and make sure there is a big chunk of color in the field CalendarColorGlob. If there isn't, run the upon opening script again.
-> '''3.''' If that doesn't get any color visible in that field (it should be visible in the field without you having to enter the field with your cursor), copy and paste the contents of that field from an uncloned copy of the file.
-> '''4.''' Finally make sure the value list of possible statuses (or whatever value list you're using as possible values for ''your'' color coded field) matches the list of values shown in the Assign Colors layout.
-> '''2.''' If no events show up with colors navigate to the Calendar Rows layout in layout mode and make sure there is a big chunk of color in the field CalendarColorGlob. If there isn't, run the upon opening script again.
-> '''3.''' If that doesn't get any color visible in that field (it should be visible in the field without you having to enter the field with your cursor), copy and paste the contents of that field from an uncloned copy of the file.
-> '''4.''' Finally make sure the value list of possible statuses (or whatever value list you're using as possible values for ''your'' color coded field) matches the list of values shown in the Assign Colors layout.
Changed lines 34-35 from:
-> If no events show up with colors navigate to the Calendar Rows layout in layout mode and make sure there is a big chunk of color in the field CalendarColorGlob. If there isn't, run the upon opening script again.
to:
-> If no events show up with colors navigate to the Calendar Rows layout in layout mode and make sure there is a big chunk of color in the field CalendarColorGlob. If there isn't, run the upon opening script again. If that doesn't get any color visible in that field (it should be visible in the field without you having to enter the field with your cursor), copy and paste the contents of that field from an uncloned copy of the file.
Changed lines 36-44 from:
-> Finally make sure the value list of possible statuses (or whatever value list you're using as possible values for ''your'' color coded field) matches the list of values you've colored on your Sources No X layout.
-> If some/all your events come up colored black, check the color tab of your "Sources No X" layout, a couple things need to be true about this list of colors:
--> There must be at least 2 items there, hence we begin our list with "Edit the colors below".
--> No event color should be the same a the default color for the text object itself (the color that shows in the formatting bar). "Edit the colors below" can / should be the default color.
--> Items of the same color need to be separated by an item of a different color (even if that isn't a "real" status).
-> If some/all your events come up colored black, check the color tab of your "Sources No X" layout, a couple things need to be true about this list of colors:
--> There must be at least 2 items there, hence we begin our list with "Edit the colors below".
--> No event color should be the same a the default color for the text object itself (the color that shows in the formatting bar). "Edit the colors below" can / should be the default color.
--> Items of the same color need to be separated by an item of a different color (even if that isn't a "real" status)
to:
-> Finally make sure the value list of possible statuses (or whatever value list you're using as possible values for ''your'' color coded field) matches the list of values shown in the Assign Colors layout.
Changed lines 16-17 from:
-> The portal on the left
to:
-> The portal on the left is based on records from the CalendarColors table and the "new status" button will make a new record in that table so you can create as many "statuses" as you want.
-> The portal is sorted by the value list "Status" so you'll want to keep that value list in synch with the contents of this portal. We use a by-hand value list here instead of basing the value list on CalendarColors records because we like how you can specify the sort order of a value list and use separators ("-") that you can't when you base a value list on a field.
-> You can '''override the color''' of any status by simply typing a new RGB value into each row.
-> You can easily alter the pallets of possible colors by editing the field definition for the field "CalendarInterface::ColorRGBValues" where the RGB values of each pallet are declared.
-> The portal is sorted by the value list "Status" so you'll want to keep that value list in synch with the contents of this portal. We use a by-hand value list here instead of basing the value list on CalendarColors records because we like how you can specify the sort order of a value list and use separators ("-") that you can't when you base a value list on a field.
-> You can '''override the color''' of any status by simply typing a new RGB value into each row.
-> You can easily alter the pallets of possible colors by editing the field definition for the field "CalendarInterface::ColorRGBValues" where the RGB values of each pallet are declared.
Added lines 11-13:
%center% %width=500px% https://www.seedcode.com/rootimages/stikipad/nextcal/assigncolors.png
Changed lines 3-10 from:
The calendar colors events based on the contents of a field of your choosing. We call this field the event "status" in the documentation, but you can use any field you'd like.
Setting up color coding is done on the Source No X layout (Source No 1, Source No 2, etc.) you made when [[integration | 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.
Below that field you'll see a section for assigning colors. Edit the list of "statuses" there in layout mode so that it matches the possible contents of the field you're using for colors. Items left blank, and items left blank, are rendered without color.
We also have 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::z_sc_ColorCalc) begins with a Let() statement were you can specify which field is being used for your colors.
Setting up color coding is done on the Source No X layout (Source No
We also have a color field in
to:
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 [[integration | 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.
-> (Note: We also have 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::z_sc_ColorCalc) begins with a Let() statement were you can specify which field is being used for your colors.)
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.
A few notes about how this works...
-> The portal on the left
Setting up color coding begins on the Source No X layout (Source No 1, Source No 2, etc.) you made when [[integration | 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.
-> (Note: We also have 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::z_sc_ColorCalc) begins with a Let() statement were you can specify which field is being used for your colors.)
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.
A few notes about how this works...
-> The portal on the left
Changed lines 29-31 from:
--> No event color should be the same a the default color for the text object itself (the color that shows in the formatting bar). "Edit the colors below" can / should be the default color.
to:
--> No event color should be the same a the default color for the text object itself (the color that shows in the formatting bar). "Edit the colors below" can / should be the default color.
--> Items of the same color need to be separated by an item of a different color (even if that isn't a "real" status).
--> Items of the same color need to be separated by an item of a different color (even if that isn't a "real" status).
Changed lines 25-26 from:
-> If all your events come up colored black, check the color tab of your "Sources No X" layout, a couple things need to be true about this list of colors:
to:
-> If some/all your events come up colored black, check the color tab of your "Sources No X" layout, a couple things need to be true about this list of colors:
Changed lines 26-27 from:
--> there must be at least 2 items there, hence we begin our list with "Edit the colors below".
-->no event color should be the same a the default color for the text object itself (the color that shows in the formatting bar). "Edit the colors below" can / should be the default color.
-->
to:
--> There must be at least 2 items there, hence we begin our list with "Edit the colors below".
--> No event color should be the same a the default color for the text object itself (the color that shows in the formatting bar). "Edit the colors below" can / should be the default color.
Changed lines 23-27 from:
-> Finally make sure the value list of possible statuses (or whatever value list you're using as possible values for ''your'' color coded field) matches the list of values you've colored on your Sources No X layout.
to:
-> Finally make sure the value list of possible statuses (or whatever value list you're using as possible values for ''your'' color coded field) matches the list of values you've colored on your Sources No X layout.
-> If all your events come up colored black, check the color tab of your "Sources No X" layout, a couple things need to be true about this list of colors:
--> there must be at least 2 items there, hence we begin our list with "Edit the colors below".
--> no event color should be the same a the default color for the text object itself (the color that shows in the formatting bar). "Edit the colors below" can / should be the default color.
-> If all your events come up colored black, check the color tab of your "Sources No X" layout, a couple things need to be true about this list of colors:
--> there must be at least 2 items there, hence we begin our list with "Edit the colors below".
--> no event color should be the same a the default color for the text object itself (the color that shows in the formatting bar). "Edit the colors below" can / should be the default color.
Changed lines 13-14 from:
Yes. Toward the end of the script "Load Calendar Settings - On Startup..." you'll see a setting for this: set that to "1". Then, on each of your "Source No X" layouts, edit the assign color section so that it just contains the name of your source in the color you'd want to see. This souce name must match the source name used on the fist tab of you "Source No X" layout.
to:
Yes. Toward the end of the script "Load Calendar Settings - On Startup..." you'll see a setting for this: set that to "1". Then, on each of your "Source No X" layouts, edit the assign color section so that it just contains the name of your source in the color you'd want to see. This source name must match the source name used on the fist tab of you "Source No X" layout.
Changed lines 11-14 from:
!! Can I color code by [[Multiple Sources| Source]] instead of by a field?
Yes. Toward the end of the script "Load Calendar Settings - On Startup..." you'll see a setting for this: set that to "1". Then, onthe
Yes. Toward the end of the script "Load Calendar Settings - On Startup..." you'll see a setting for this: set that to "1". Then, on
to:
!! Can I color code by Source instead of by a field?
Yes. Toward the end of the script "Load Calendar Settings - On Startup..." you'll see a setting for this: set that to "1". Then, on each of your "Source No X" layouts, edit the assign color section so that it just contains the name of your source in the color you'd want to see. This souce name must match the source name used on the fist tab of you "Source No X" layout.
Yes. Toward the end of the script "Load Calendar Settings - On Startup..." you'll see a setting for this: set that to "1". Then, on each of your "Source No X" layouts, edit the assign color section so that it just contains the name of your source in the color you'd want to see. This souce name must match the source name used on the fist tab of you "Source No X" layout.
Changed lines 11-12 from:
!! Can I color code by [[Multiple Sources]] Source instead of by a field?
to:
!! Can I color code by [[Multiple Sources| Source]] instead of by a field?
Added lines 11-14:
!! Can I color code by [[Multiple Sources]] Source instead of by a field?
Yes. Toward the end of the script "Load Calendar Settings - On Startup..." you'll see a setting for this: set that to "1". Then, on the
Yes. Toward the end of the script "Load Calendar Settings - On Startup..." you'll see a setting for this: set that to "1". Then, on the
Changed lines 3-4 from:
to:
The calendar colors events based on the contents of a field of your choosing. We call this field the event "status" in the documentation, but you can use any field you'd like.
Setting up color coding is done on the Source No X layout (Source No 1, Source No 2, etc.) you made when [[integration | 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.
Below that field you'll see a section for assigning colors. Edit the list of "statuses" there in layout mode so that it matches the possible contents of the field you're using for colors. Items left blank, and items left blank, are rendered without color.
We also have 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::z_sc_ColorCalc) begins with a Let() statement were you can specify which field is being used for your colors.
Setting up color coding is done on the Source No X layout (Source No 1, Source No 2, etc.) you made when [[integration | 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.
Below that field you'll see a section for assigning colors. Edit the list of "statuses" there in layout mode so that it matches the possible contents of the field you're using for colors. Items left blank, and items left blank, are rendered without color.
We also have 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::z_sc_ColorCalc) begins with a Let() statement were you can specify which field is being used for your colors.
Changed lines 13-19 from:
to:
Here are some tips to make sure color coding works as you expect.
-> Make sure that the field you use for color mapping on the Source No X layout, and the field you use in SampleEvents::z_sc_ColorCalc are the same fields.
-> If no events show up with colors navigate to the Calendar Rows layout in layout mode and make sure there is a big chunk of color in the field CalendarColorGlob. If there isn't, run the upon opening script again.
-> Finally make sure the value list of possible statuses (or whatever value list you're using as possible values for ''your'' color coded field) matches the list of values you've colored on your Sources No X layout.
-> Make sure that the field you use for color mapping on the Source No X layout, and the field you use in SampleEvents::z_sc_ColorCalc are the same fields.
-> If no events show up with colors navigate to the Calendar Rows layout in layout mode and make sure there is a big chunk of color in the field CalendarColorGlob. If there isn't, run the upon opening script again.
-> Finally make sure the value list of possible statuses (or whatever value list you're using as possible values for ''your'' color coded field) matches the list of values you've colored on your Sources No X layout.
Added lines 1-7:
!! How are events color coded?
overview
!! Troubleshooting Colors
making sure color mapping and color calc use the same fields
overview
!! Troubleshooting Colors
making sure color mapping and color calc use the same fields
