Event Colors
SeedCodeComplete2.EventColors History
Hide minor edits - Show changes to output
Added lines 28-43:
!! Can I color by a field outside the Event, like the Event's Project's Status?
Yes.
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. That calc could begin...
Let ( [
-> p = CalendarEventsProjects::Status ;
-> 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.
Yes.
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. That calc could begin...
Let ( [
-> p = CalendarEventsProjects::Status ;
-> 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.
Changed lines 5-8 from:
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.)
-> (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 (
to:
Setting up color coding begins on the Source No 1 layout (Source No 1, Source No 2, etc.) you made when [[calendar configuration | configuring]] 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 (CalendarEvents::z_sc_ColorCalc) begins with a Let() statement were you can specify which field is being used for your colors.)
-> (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 (CalendarEvents::z_sc_ColorCalc) begins with a Let() statement were you can specify which field is being used for your colors.)
Changed lines 32-33 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::z_sc_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 CalendarEvents::z_sc_ColorCalc are the same fields.
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% http://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
