在网上搜了一大圈,最后在同事的帮助下,找到了个英文网站,问题总算解决了。呵呵!
Solution 1:
You may change symbol and other format properties on client. Below is example to change symbol on client.
Note: You should keep in mind that persistance of those values is not supported and after a postback format will return to original server format.
<script type="text/javascript">
function changeSymbol()
{
var edit = igedit_getById('<%=WebCurrencyEdit1.ClientID%>');
var val = edit.getValue();
edit.symbol = '¥';
//edit.positivePattern = 'n$';
//edit.decimalSeparator = ',';
//edit.groupSeparator = '.';
edit.setValue(val);
}
</script>
<input type="button" value="Change$" οnclick="changeSymbol()" />
<igtxt:WebCurrencyEdit ID="WebCurrencyEdit1" runat="server"></igtxt:WebCurrencyEdit>
Solution 2:
aspx:
<igtxt:WebCurrencyEdit ID="WebCurrencyEdit1" runat="server" ValueText="12"></igtxt:WebCurrencyEdit>
<asp:Button ID="Button1" runat="server" Text="Button" οnclick="Button1_Click" />
aspx.cs:
protected void Button1_Click(object sender, EventArgs e)
{
System.Globalization.CultureInfo ci = System.Globalization.CultureInfo.CreateSpecificCulture("en-US");
ci.NumberFormat.CurrencySymbol = "XX";
this.WebCurrencyEdit1.NumberFormat = ci.NumberFormat;
}
Note: you should keep in mind that changes to Culture do not persist. If you changed something conditionally and that condition is not used for following sessions, then all your conditional custom settings will be lost. If you have another submit button, then after click on that button the "XX" symbol will be lost and default "$" will be used. But that has nothing to do with editor, but with CultureInfo which persistance is not supported by .NET. It means that if you need to customize culture, then you should do that in every single session, for example, within Page.OnLoad event.