Dietrich Streifert schrieb:
> I had a look at the invisible menu button problem:

That's great. Thank you.

> 
> The menu button (created in Table.js, line 172: 
> this._columnVisibilityBt) is an instance of qx.ui.toolbar.Button:
> 
>     this._columnVisibilityBt = new qx.ui.toolbar.Button(null, 
> "widget/table/selectColumnOrder.png");

I don't think it is a good idea to use a toolbar button at all. I think 
to replace it with a button and set the appearance to something like 
"table-menubar-button" should be the better solution. Normally after 
this change you should not have anymore a problem with conflicting defaults.

Can you try it again with this idea?

Sebastian

> 
> If instead qx.ui.form.Button is used the button is visible again but has 
> the wrong dimensions. Forcing the width and height to 16 (by calling 
> setWidth and setHeight after instantiation) sets the right dimensions to 
> the button. This is the solution which comes closest to the previous 
> look but is not the same as in 0.6
> 
> So I suspect that something with qx.ui.toolbar.Button (or form.Button or 
> Atom) is broken or default appearance changed in 0.7.
> 
> 
> I tried to force dimensions of qx.ui.toolbar.Button by setting the 
> dimensions in the constructor parameter list:
> 
>     this._columnVisibilityBt = new qx.ui.toolbar.Button(null, 
> "widget/table/selectColumnOrder.png", 16, 16);
> 
> which lead to the following error:
> 
> this._iconObject has no properties
> http://nra/qooxdoo.dev/frontend/framework/source/class/qx/ui/basic/Atom.js
> Line 520
> 
> 
> Again I tried to replace this with an instance of qx.ui.form.Button:
> 
>     this._columnVisibilityBt = new qx.ui.toolbar.Button(null, 
> "widget/table/selectColumnOrder.png", 16, 16);
> 
> which succeded but setting width and height within the constructor is 
> ignored.
> 
> My knowledge of the new appearance and property system is very limited 
> so I don't think I'm able to solve this issues.
> 
> I can check in the solution with the replacement of toolbar.Button with 
> form.Button if this helps, but I think the underlaying problems should 
> be solved first.
> 
> Regards....
> 
> 
> Sebastian Werner schrieb:
>> Hi All,
>>
>> can someone of the Table developers e.g. Til, Derrell, etc. take a look 
>> at the current implementation and help us to fix it? It would be really 
>> helpful as I have no deep understanding of the implementation.
>>
>> The table itself gets initialized correctly, but there are some issues:
>>
>> * the menu button inside the column headers is not visible.
>> * the editing feature seems not to work, after editing a cell, the cell 
>> is empty or shows NaN.
>>
>> I think that most of the issues are related to the property system which 
>> behaves differently compared to the old one. I really hope that we get 
>> fixed this as soon as possible.
>>
>> Thank you for your help.
>>
>> Sebastian
>>
>> -------------------------------------------------------------------------
>> 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
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>   
> 


-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to