Calendar background is red when schedules removed

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I'm using ActiveX Suite Pro 16.4.

After building a calendar with multiple schedules, the user can choose which attendee's schedules appear by checking or unchecking boxes.  If the user happens to remove all schedules, the calendar background turns bright red.

Is there a property that controls the color of this background? The red is too bright and users think an error has occurred. I'd like to change it to a neutral color.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
iliketurtles Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 25 January 2017 Status: Offline Points: 12	Post Options Post Reply Quote iliketurtles Report Post Thanks(0) Quote Reply Topic: Calendar background is red when schedules removed Posted: 26 June 2017 at 4:17pm
	I'm using ActiveX Suite Pro 16.4. After building a calendar with multiple schedules, the user can choose which attendee's schedules appear by checking or unchecking boxes. If the user happens to remove all schedules, the calendar background turns bright red. Is there a property that controls the color of this background? The red is too bright and users think an error has occurred. I'd like to change it to a neutral color.

olebed Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 01 July 2014 Location: Ukraine Status: Offline Points: 841	Post Options Post Reply Quote olebed Report Post Thanks(0) Quote Reply Posted: 17 July 2017 at 7:44am
	Hello iliketurtles, I think we have fixed this red color. Have you tried v17.3 or v18.0 ? Regards, Oleksandr Lebed

iliketurtles Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 25 January 2017 Status: Offline Points: 12	Post Options Post Reply Quote iliketurtles Report Post Thanks(0) Quote Reply Posted: 19 September 2017 at 4:32pm
	I have not tried the new version yet, but thank you for the fix. We've worked around it for now.