Hi Alex,

This method is same like your method to apply the css inside WebScheduler. But if you're using your method, you should set all style in your css to replace our style that you defined in WebScheduler.css (you couldn't set background color only or etc). Although, with this method the style couldn't be read in our server side.

To resolve this issue, you could change some of the style in style tag. With this method, our exporting API could read the css for its default style. Regarding to your sample, here's the class name that you should override:

SchedulerViewHeaderStyleNormal: WSB1_VH-N
SchedulerFrameStyle: WSB1_SchedulerFrameStyle
SchedulerMonthInBoundDateHeaderStyleNormal: WSB1_MIDH-N
SchedulerMonthOutboundDateHeaderStyle: WSB1_MODH-N
SchedulerContentCell: WSB1_TimelineContentCellStyle
SchedulerCalendarFrameStyle: WSB1_CalendarFrameStyle
SchedulerCalendarHeaderStyle: WSB1_CalendarHeaderStyle
SchedulerCalendarTableStyle: WSB1_CalendarTableStyle
SchedulerCalendarSelectedCellStyle: WSB1_CalendarSelectedCellStyle

Hope this helps.

Regards,
Bernard

Hi Joseph,

I can replicate your issue here. This issue has been handled in our Work Item #1564. I will let you know any news regarding this work item. Thank your for your valuable feedback.

Regards,
Bernard

Hi Alex,

Sorry for our late responses. I have found where all those issue comes from.

For your first issue, it says that value of FontSize is out of range. This problem happen because when reporting our WebScheduler use 3rd party assembly to export WebScheduler. So it has limited capability to change the style in WebScheduler. However, you can resolve this by comment these line in SigmaScheduler.cs

this.ViewHeaderStyle.Normal.CssClass = "SchedulerViewHeaderStyleNormal";
this.SchedulerFrameStyle.CssClass = "SchedulerFrameStyle";
this.MonthInboundDateHeaderStyle.Normal.CssClass = "SchedulerMonthInBoundDateHeaderStyleNormal";
this.MonthOutboundDateHeaderStyle.Normal.CssClass = "SchedulerMonthOutboundDateHeaderStyle";
this.TimelineContentCellStyle.CssClass = "SchedulerContentCell";
this.CalendarFrameStyle.CssClass = "SchedulerCalendarFrameStyle";
this.CalendarHeaderStyle.CssClass = "SchedulerCalendarHeaderStyle";
this.CalendarTableStyle.CssClass = "SchedulerCalendarTableStyle";
this.CalendarSelectedCellStyle.CssClass = "SchedulerCalendarSelectedCellStyle";

For the second issue, this issue happen because WebScheduler_Year.js couldn't be load because you couldn't show Year view in your scheduler. You could load the js or enable year view in scheduler. But it will be better to enable Year View so it won't make error in our API.

For the third issue, actually, we can replicate this issue in our local end and we consider this as bug. We will fix it soon and add this as Hotfix. In while, you could put ISDataSource runtime license key in your project to resolve this issue.

Hope this helps.

Regards,
Bernard

Hi Alexandre Liard,

Actually, you couldn't get the IFrame's ID inside WebTextEditor because it will be created by our API in client-side. Although, you could bind the content to iframe in your server side by using this function:

WebTextEditor1.LoadContentFromFile(Server.MapPath("./SampleHtml/Product Overview.html"), true);

You can see the sample in here http://live.intersoftpt.com/cs/WebTextEditor/WebTextEditor/SaveAndLoadContentToFile.aspx?noframe=1&path=/WebTextEditor/Rich%20Text%20Editor/Advanced%20Client-side%20and%20Server-side%20Programmability

Or you can populate the data from server side and send it to client side, then client side will set the value regarding its iframe ID. You can set the text using this SetValue function. See the sample here:

http://live.intersoftpt.com/cs/WebTextEditor/WebTextEditor/SetValueFromClientSide.aspx?noframe=1&path=/WebTextEditor/Rich%20Text%20Editor/Advanced%20Client-side%20and%20Server-side%20Programmability

If this matter doesn't resolve your problem, could you explain me the scenario that you want to achieve with WebTextEditor? Maybe with your scenario I can figure out some method to achieve your scenario. Look forward to hear any feedback from you so I can help you further.

Regards,
Bernard

Hi Alexandre, 

I tried to replicate your issue in our sample. Unfortunately, I couldn't replicate this issue in our local end. As you can see in our sample (Exporting_ServerSide.aspx), it using the same method that you mentioned before except the SelectedViewMode changing. But when I applied that code in our sample, exporting executed perfectly. Is there any steps of configuration that you used to replicate this issue in your local? Maybe some steps or sample will help us to determine where this problem comes from. Look forward to hear any feedback from you so I can help you further.

Regards,
Bernard