Web Custom Controls 1.3.3 Released
Web Custom Controls 1.3.3 has been released. This version fixes a conflict/compiler error due to a change made in Xojo 2014r3 (currently in beta testing). Web Custom Controls 1.3.3 also adds a significant performance enhancement to WebListBoxTD. If you are going to add, edit, or delete multiple rows in a loop, set CacheScripts to TRUE before the loop and FALSE after. This hint lets WebListBoxTD...
Read MoreWeb Custom Controls 1.3.2 Released
Web Custom Controls 1.3.2 has been released. Version 1.3.2 fixes the bugs that were related to changes in Xojo 2014r2 and 2014r2.1. This is a free update for all registered users. My apologies to those of you who were waiting on these bug fixes. The changes for 2014r2.1 were a little more involved then I had anticipated.
Read MoreRunning on Xojo 2014r2.1
Note: Web Custom Controls 1.3.2 has been released and includes updates for Xojo 2014r2.1. Please download the latest version to resolve any issues with Xojo 2014r2.1. Xojo 2014r2.1 has been released today. As some of you noticed during the beta period, r2.1 introduced a few changes which caused problems for Web Custom Controls. I’ve been waiting until the final, public release because at...
Read MoreRunning on Xojo 2014r2
Note: Web Custom Controls 1.3.2 has been released and includes the fix discussed below. Please download the latest version to resolve this issue. I’m still dragging behind on my work list. Way behind. Unfortunately I’ve also found a couple of other issues with wcc on Xojo 2014r2. I really don’t want to prepare and release an update unless I’m going to fix those issues as...
Read MoreXojo 2014 r2 Issue
Some users are running into an issue with Web Custom Controls 1.3.1 and Xojo 2014r2. Web Custom Controls 1.4 is still in progress, so I’m going to release a 1.3.2 patch later today. The issue looks scary, i.e. the controls won’t load with a security error. But the fix is actually trivial. It’s related to a corrupted HTML header. It looks like Xojo 2014r2 wants to set the header...
Read MoreChrome & jCanvas
While testing the upcoming Web Custom Controls 1.4 release I ran into a jCanvas bug which only appeared on Chrome. Basically an animation using the built in jQuery animator would cause the window to go blank leaving only the content of the canvas element. (The frames based animator I created for Xojo was unaffected.) I could consistently reproduce it on Mac and Windows. The strange thing about...
Read MoreWork Around for WebControl.Page Returning Nil
I’m posting a work around to the feedback issue discussed in this forum post, 29484 Page Property Of Control On WebToolbarContainer Returns Nil. Simply download this Xojo module and add it to your web project. Then call FindPageTD instead of Page in code where Page is returning Nil. FindPageTD has to search all of the controls on all of the pages for the session. A typical Xojo web app is...
Read MoreFixed in 2013r4.1: jQueryFileUpload Requires Xojo 2013r2 For Now
This issue has been fixed in Xojo 2013r4.1. jQueryFileUpload is working correctly with 2013r4.1. Update 9/23/2013: Here’s the feedback report: feedback://showreport?report_id=29775 I believe that this only affects the jQueryFileUpload control and that the rest of the controls are working properly under r3. So if you do not use the jQueryFileUpload control your project should be fine in r3....
Read MoreA Note About jCanvas & JSONItem Performance
While preparing and testing Web Custom Controls 1.3.1 I noticed a significant drop in jCanvas animation performance. I’ve traced this issue back to the JSONItem class. Something changed recently in JSONItem and this has caused a 2-4x decrease in the performance of the Value method. The change must have occurred with RS2012r2 or r2.1 because the previous stand alone demo, compiled with...
Read MoreSessions and WebSessionContext on Xojo
Xojo 2013r1 has a bug in the WebSessionContext object: feedback://showreport?report_id=27067 As a result, you cannot expect the Session function to work and return a WebSession when called in a Web Custom Control event. You can, however, access the session for the event from the control. Simply call: Me.EventSession Unfortunately this can result in other subtle bugs. For example, calling certain...
Read More