Did anyone get Leo's update to work?

We tried in vain for 6 hours to get the update to work to no avail. Our webscheduler control is still broken after users updated to chrome 43.

We are having the exact same issue as outlined in Michal Podbielski's post. Our webscheduler is unusbale and our commercial app is broken.

Please advise!

Frank Gary

The new version of chrome has caused the webscheduler control to improperly render causing the control to be unusable. Reverting chrome back to previous version works fine until it auto updates the users browser over and over again and it appears there is no way to stop the auto chrome update without hacking the users registry.

Please help as our application is centric to the webscheduler control!

Frank Gary

Hi Yudi -

Thanks for the reply which helped us to move a step further in troubleshooting this issue. Below are the  steps undertaken and our findings :

1) We get rid of all the data binded to the webscheduler which inturn make the export PDF functionality   to work,which means it is definitely something with the binded data or how webscheduler is interpreting   data.

2) Strangely we notice some bizzare things with the exported PDF which you can also see in the attached exported PDF in the reply.

     a) We have set the webscheduler to only show time starting from   "07:00 AM - 11:00 PM" but if you          see the exported PDF it actually exported from "12:00 AM - 04:00 PM". It looks like it is some how            shifting the time to -7 hrs,might be a timezone shift ?

     b) We also believe that this might be the reason we are getting a "date error" for export since it might        be shifting the time on the color bars like it is doing with the header times.

3) Also the layout seems to be odd. It only shows 3 times horizontaly when there is space for more.

Hope we have provided all the information required to reproduce and get this issue fixed. Looking           forward for a prompt reply.

Thanks!

Ok, so this time we were able to run your sample and it is working but that's not how we were looking forward to it to work. If you read our previous replies you can see that we were able to get the resources and latest data updated on the webscheduler if we do a page refresh (or a POSTBACK to server) but we can't do that because we need to preserve the state of page and as we can see in your modified page code that you are doing a POSTBACK on value change of the dropdown and that's how it is working in your sample.

We have modified you sample with some of our modified code and attaching those for your refrence ('ModifiedFiles_AndHandler') that how we trying to get it work without POSTBACK or page refresh.If you unzip the attached zip folder you can find two of your own modified files and one folder where we have added a Handler to update the Session variable 'resourceid'.Below mentioned are the changes we made to your code to make it look alike as per our current code.

> 'WSUsingSessionInSelectMethod_Modified.aspx' : AutoPostBack is set to 'False' for Dropdown so there is no page reload.

> 'WSUsingSessionInSelectMethod_Modified.aspx' : Attached a Javascript code on 'Change' event of dropdown to update the Session variable 'ResourceID' with the help of a Handler ('ControlBoard_UpdateSessionVariable') and then calling 'Webscheduler.Refresh()'. Note :* You need to include Javascript library file in your code.

> 'WSUsingSessionInSelectMethod_Modified.aspx.cs'  : Modified your 'ISDataSource1_Selecting' event to pass Session["ResourceID"] value to e.InputParameters["ID"] instead of DropDownList1.SelectedValue.ToString(); since dropdown no longer posting value back to server.

After making the above mentioned changes we found that 'Webscheduler.Refresh()' and 'Webscheduler.RefreshResources()' they both don't update the webscheduler until and unless the Page is refreshed in your sample also even though the input parameter value is right.

Hope you can have a better understanding of our problem now and may you just let us know whether it is possible to refresh resources on the page without doing a postback or pageload by using control client side event webscheduler.Refresh() or webscheduler.RefreshResources().

Thanks - Frank

We tried this code yudi but somehow it didn't work for us. Attached in the reply is a video (2014-06-19_1527_RefreshResources_NW) showing how "RefreshResources()" function didn't update the "ResourceName" but a "Refresh()" do update the "ResourceName" but thats one thing ,the major issue is we don't want just the resource names to be updated but we want the interface to load all the resources of the selected company from the dropdown so that the data is visible on the webscheduler control board. Right now whats happening is it loads the right data for the selected company resources but since the resources are not updated on the interface the data does not get plotted.

For better explanation of the above problem please refer to attach video (2014-06-19_1539_PageRefreshWork).In this video you can see we have a company dropdown on the page and on its change we have a jquery event which make a ajax call to a handler to update the session variable for the selected company (context.Session["WebScheduler.ViewSettings.SelectedCompany"]) and once it does that we call Scheduler.Refresh() function . When we call refresh for scheduler call the "ISDataSource1_Selecting" event to re-bind the data and resources depending upon any change which in our case should load data and resources for the changed company. You can see that it hit the breakpoint in code (e.ViewName == "Nop_Resource") and pass the selected company id as parameter since to load resource we are using a StoredProcedure. Every things look ok but as soon the call retuned back to the page we can see the resources were unchanged and no data is visible since data is updated but not the resources so new data didn't get plotted. Further you can see if we do a complete page refresh on the selection of company from dropdown every thing work fine.

This is really getting complicated now because we can't refresh the whole page since by doing that user will loose their current state of page and we really don't want that and because of this problem we are not able to release this code.

Hope we can expedite this issue and get it resolved ASAP.

Thanks - Frank