Community
Participate
Working Groups
Build Identifier: 0.7.0.v201111130901 Open the attached handler, below exception is thrown. Also, it's interesting that in my EGL source code, the pattern is "yyyyMMddHHmmssffffff", while in the exception stack, it prints 'yyyyMMddHHmmssSSSSSS'. Could not render UI [CRRUI2032E] 时间戳记模式 yyyyMMddHHmmssSSSSSS 无效 [CRRUI2094E] 以下是导致此错误的 EGL 函数调用: DojoTimeTextBox.DojoTextBase._setEvent() [native JavaScript] DojoTimeTextBox.DojoValidationBase._setEvent() [native JavaScript] DojoTimeTextBox.DojoTimeTextBox._setEvent() [native JavaScript] DojoTimeTextBox.DojoTextBase.installEventHandlers() [native JavaScript] DojoTimeTextBox.DojoValidationBase.installEventHandlers() [native JavaScript] DojoTimeTextBox.DojoTimeTextBox.installEventHandlers() [native JavaScript] uncaught exception: [type=eglx.lang.AnyException, message=[CRRUI2032E] öô3°! yyyyMMddHHmmssSSSSSS àH] :0 [CRRUI2095E] 未能找到导致此错误的 EGL 函数调用 Reproducible: Always
Created attachment 206912 [details] The sample EGL file.
Set the defect severity to major.
We're only using timestamp with this control because time is unsupported in 0.7. For 1.0 time will be back and this control will go back to using a time value instead of timestamp. Therefore there is the requirement, for 0.7, that you use the format "HHmmss" on your timestamp field if you wish to use it with the DojoTimeTextBox control.
(In reply to comment #3) > We're only using timestamp with this control because time is unsupported in > 0.7. For 1.0 time will be back and this control will go back to using a time > value instead of timestamp. Therefore there is the requirement, for 0.7, that > you use the format "HHmmss" on your timestamp field if you wish to use it with > the DojoTimeTextBox control. Thanks Justin... But I'm curious that why I specified pattern yyyyMMddHHmmssffffff, while it prints yyyyMMddHHmmssSSSSSS in the error stack trace?
The 'S' format in the error message is very minor, we won't fix that in 0.7.
Created attachment 208364 [details] Fix for the exception message
Fix the problem mentioned in comment 4.
Verified in 0.8.0.v201201150902-1CT-Fiv5_M5_LOPfUa4.