Topic Details - PeterBlum.com

Sorry, we're closed.

PeterBlum.com was active from 2002 - 2013, when ASP.NET Web Forms were all the rage.

Thanks for your patronage!

Feel free to browse this preserved snapshot of the products, demos, and documentation from those days. Then hop over to github.com/plblum to see what Peter's been working on lately.

Software Releases

Back

ID: 00082

Posted on: 11/12/2012

Peter's Data Entry Suite 5.0.3 Update

New features:

IntegerTextBox, DecimalTextBox, CurrencyTextBox, and PercentTextBox now offer the AllowThousandsSeparator property. By default, users can type in the thousands separator symbol. When this is false, they cannot and if validation finds this character, it causes validation error.
IE 10 has poor support for filter styles, a feature introduced by Microsoft in IE 5.5 that provides the shadow and fade-in/out effects used by DES’s popup elements. The result is a JavaScript error on that browser. IE 10 is now detected and these features are disabled.
Compatibility with Telerik RadControls 2012 Q3 release. Telerik had made changes in their client-side API making some controls have a JavaScript error and others not validate correctly.

Bug fixes:

Design mode would report an error instead of drawing the control in several cases, due to a bug introduced in v5.0.2
Popup calendar sometimes did not engage keyboard support after a second popup.
Popup toggle buttons for calendar, monthyearpicker, and timepicker all should have closed the popup when opened. They left it open. These buttons now act as a true toggle.
Client-side calculation for the length of a string in a textbox counted carraige returns incorrectly on modern browsers. FireFox 15+, IE 9+, and Safari 5+ changed how many characters they stored in memory for each carraige return from two characters (ASCII 13+ ASCII 10) to ASCII 10 alone. On the server side, the browsers always postback ASCII 13+ASCII 10. Now TextLengthValidator and TextCounter control count 2 characters for each carraige return even if they store only 1 character on the client-side.
The value of the marked checkbox in a CheckBoxList did not work with the CompareToValueValidator or CompareToValueCondition on the client-side.
When JavaScript is detected to be disabled, some scripts were still written to the page.
The mouse over and mouse down effects of some buttons with images did not work. This was noticable on the Calendar’s next and previous month/year buttons.
VisibleCondition, EnabledCondition, and ReadOnlyCondition did not evaluate correctly on the client-side.
Calendar part showing the month and year names did not apply the correct style sheet based on the MonthYearCommandAndLabel.CssClass property. It worked initially but a mouse over would apply an incorrect class.
CalculationController’s attempted to assign a decimal value to an IntegerTextBox causing a TypeCastException when the ShowValueControlID specified an IntegerTextBox.
Using the Input Security module’s LogAndRespond system to track an exception or error would cause a NullReferenceException if tracking an error when using an HttpHandler other than one that loads the page.
The DecimalTextBox, CurrencyTextBox, and PercentTextBox would return the value of Int32.MinValue instead of Double.MinValue when you call their DoubleBindable property and there is no value assigned yet.
The ValidationManager.OnAdjustValidatorToBrowser event would cause a NullReferenceException if the browser cause the ErrorFormatter to be replaced. Impacted webcrawlers.

BLD bug fixes:

Server-side UI-level validation for the RequiredAttribute failed.
Currency FieldTemplates did not use the UseCurrencySymbol property from the CurrencyDataTypeAttribute.
Percent FieldTemplates did not use the UsePercentSymbol property from the PercentDataTypeAttribute.
Several exceptions raised by the Filter controls.

Illegal characters detected in an input