Studio for LightSwitch 2013 v2 is released with several new features and bug fixes. This version of Studio for LightSwitch HTML is powered by Wijmo Professional version 3.20131.7
This topic has a complete list of the enhancements and fixes included in 2013 v2 release. If you have a licensed ComponentOne Studio for LightSwitch installed in your system, you can download and install this upgrade for free. Please contact sales in case you have any query or you want to know more about the available options.
ComponentOne Studio for LightSwitch includes the following products:
- ComponentOne Studio for LightSwitch HTML
- ComponentOne Studio for LightSwitch Desktop
New in 2013 v2 Release
Dependencies:
The NuGet package Wijmo for LightSwitch HTML Client depends on jQuery Mobile 1.3.2 version. This is added to remove the errors that occurred in the earlier versions.
Platform/Environment Changes:
ComponentOne Studio for LightSwitch has a major version number of 2.0, and the extensions in ComponentOne Studio for LightSwitch Desktop are built with Visual Studio 2012 using Silverlight 5 assemblies to fix the following issues:
- For Visual Studio 2012 Update 3, use Desktop and HTML clients in separate LightSwitch projects. In case you add a desktop project that already contains one or more Studio for Desktop extensions to an HTML project, a build error, The "LSResourceGeneratorsTask" task failed unexpectedly, occurs. For now, there is no workaround for this error.
- This LightSwitch version provides support to work on Visual Studio 2013 Preview, but the platform has not been tested extensively, therefore it is recommended to use Visual Studio 2012 Update 2.
ComponentOne Studio for LightSwitch HTML, designed to target jQuery Mobile-based HTML client, offers support for the following versions of LightSwitch:
- LightSwitch in Microsoft Visual Studio 2012 (Update 2 or above).
- LightSwitch in Microsoft Visual Studio 2013 Preview.
ComponentOne Studio for LightSwitch Desktop, designed to target the Silverlight-based desktop client, offers support for the following LightSwitch versions:
- Microsoft Visual Studio LightSwitch 2011 RTM.
- LightSwitch in Microsoft Visual Studio 2012.
- LightSwitch in Microsoft Visual Studio 2013 Preview.
Added Drop Down Widget
The Drop Down widget implements HTML <select> tag that displays a combo box to select one item from the collection of items.
LightSwitch in Microsoft Visual Studio 2013 Preview
Once you have installed the NuGet client package in the HTML Client project, you need to perform an additional step:
 |
Open the file, default.htm from the HTML Client project, and change all the occurrences of 1.0.1 to 2.0.0 within the filename strings. |
Script
Enhancements:
- Added the intrinsic LightSwitch progress animation to the Wijmo OLAP Screen.
- Added the intrinsic LightSwitch progress animation to the JSON Grid and JSON Chart widgets.
- Added a new method call to the end of the generated render code for collection controls such as grids and charts and their associated screen templates.
- Added canExecute handlers to the NextPage/PreviousPage commands in the paging grid screen template.
Bug Fixes:
- [default.htm] Updated jQuery Mobile references to 1.3.1 so that JavaScript runtime error does not occur.
- Replaced IE-specific method, window.navigate, with browser-neutral code.
- [All Extensions] Fixed a bug where the Edit Render Code link continues to generate code even after the trial period has expired.
Events Calendar
Bug Fixes:
- In the events calendar screen template, paging is disabled by default.
- In list view, the list of events on the left is scrollable.
- Fixed a bug where time slots were missing in Day view after adding data using an editable grid screen.
FlexChart
Bug Fixes:
- Fixed a bug so that the line chart renders even if the underlying value type is decimal.
FlexGrid
Enhancements:
- Added allowEditing and afterCellUpdate options to facilitate in-cell editing in FlexGrid. If allowEditing is set to true, tapping a data cell will initiate editing directly within the grid. The new default setting for afterCellUpdate ensures that the model layer is updated accordingly.
- When a user taps a row header to open an edit screen, allowEditing option must be false, the grid automatically gets updated on any change committed by the user in FlexGrid.
- When the user saves/discards pending changes, the grid is automatically updated.
- Row headers display icons to indicate the entity state (modified, deleted, added).
- Added a new screen template, Wijmo Grid Screen (Editing). This template creates an edit screen with in-cell editing enabled for a scrolling grid. It also has command buttons for adding a new item or deleting the selected item.
- Added canExecute handlers to the NextPage/PreviousPage commands in the paging grid screen template.
- Added the GetRowEntity function to the object returned by c1ls.getGridContent. This function returns the underlying LightSwitch entity, given a row index.
- Updated Grid Screen template to make it easier for users to use HTML and Desktop clients within the same project.
Bug Fixes:
- Replaced the jQuery Mobile spinning wait icon with LightSwitch progress animation.
- Fixed a bug wherein adding a new row to grid created grid cells with “undefined” values.
- Fixed bug where the grid columns shifted to the left when switching tabs.
- Fixed an issue that occurred when the browser window was resized before a previously rendered grid was redisplayed.
- Fixed the bug of the paging grid screen, the grid now adheres to query filters set by other controls that were added to the default screen template.
- Fixed display issues in the paging grid screen when the page size is set to 1.
- Fixed a bug so that the columns from related tables are set to read-only and cannot be edited in-place.
- Fixed a bug that the grid did not render when used inside a tab of a details screen.
- Fixed the issue so that the grid renders also when used inside a popup element
- Fixed a bug so that when multiple grids were bound to the same collection in a single tab, not just the first grid renders.
- Fixed an issue where an error occurred while navigating to the next page after opening an editable grid screen.
- Fixed an issue where an occurred on clicking the Previous or Next button when multiple grids are bound to the same collection.
- Fixed an issue where “Screen is undefined” error occurs when a custom method is used for a Tap action.
- Fixed an issue where a user could not navigate to the last page a second time after sorting a column.
- Fixed an issue wherein all the rows are not shown in the paging screen after applying or removing a filter.
- Fixed an issue so that opening a filter dropdown in the paging screen invokes the Tap action correctly.
- Fixed an issue where users could not navigate to the next page after filtering is removed.
Rating
Bug Fixes:
- Fixed a bug where each rating icon was split into pieces if the Split option was used.