Dietrich Streifert <[EMAIL PROTECTED]> writes:
> Hi Fabian,
>
> I'm sorry but the initializer method was already called behind the
> this.base(arguments,...) call but it did not work. Here is the code of the
> constructor:
>
> construct : function(vCaption, vIcon, vWindowManager)
> {
> this.base(arguments, vCaption, (vIcon ? vIcon :
> 'icon/16/actions/documentinfo.png'), vWindowManager);
> this.initMessageIcons({
> info : "icon/16/actions/documentinfo.png",
> error : "icon/16/actions/stop.png",
> warning : "icon/16/actions/status_unknown.png",
> ok : 'icon/16/status/ok.png'
> }
> );
>
> The error is:
>
> this.initMessageIcons is not a function
> http://nra/nra/app-source/class/qx/visionet/ui/dialog/MessageDialog.js
> Line 52
>
> Anyway, if I define the property as follows:
>
> messageIcons :
> {
> check : "Object",
> init : {
> info : "icon/16/actions/documentinfo.png",
> error : "icon/16/actions/stop.png",
> warning : "icon/16/actions/status_unknown.png",
> ok : 'icon/16/status/ok.png'
> }
> }
>
> The init value is declared properly. What is the difference between
> having the initial value in the init property and assigned by the init
> method call in the constructor?
Dietrich, are you possibly hitting the same bug that has been discussed
recently, where you can't refine the init value if an init value doesn't
exist in the base class? Maybe if you put an init:null in your property
definition it will cause the initMessageIcons() method to be
generated???
(Just guessing.)
Derrell
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
