Got it. It’s a regression caused by an optimization 🙂
Now wisej is able to automatically translate widget ids from the client into widget references when receiving events. But nobody told the TreeView which tried to resolve the string id into a component when it was already a component.
BTW, you don’t need to attach/detach the key handler and handle F2. When the property LabelEdit is true, the TreeView already handles F2 to start editing. You can also start editing when clicking a second time on the same node, after a delay.
Best,
Luca
Thanks Cris.
Forgot to add that WJ-7642 is also fixed in the same release (1.2.67)
Best regards
Frank
Hi Alexander,
WJ-7634 is fixed in the latest build (1.2.67).
Best regards
Frank
Hi Alex,
WJ-7635 and WJ-7636 are both fixed in 1.2.67
Best regards
Frank
Hi Cris,
WJ-7641 is fixed in release 1.2.67
Best regards
Frank
Hi Alex,
first: I have created enhancement request WJ-7643 for the property values of NodeFont.
The problems with click/double click and the missing location are all fixed in release 1.2.67.
Best regards
Frank
A new build (1.2.67) has just been uploaded. It includes the following fixes:
| Item | Type | Priority | Severity | Title | Resolution |
| WJ-7641 | Bug | Low | Trivial | ThemeBuilder cannot load theme with . in its name | Complete |
| WJ-7642 | Bug | Low | Trivial | Theme with . in its name cannot be used at runtime | Complete |
| WJ-7634 | Bug | Low | Trivial | When concatenating embedded resources in debug mode, Wisej may add a BOM (Unicde marker) sequence making the file invalid. |
Complete |
| WJ-7639 | Bug | Medium | Major | TreeView.NodeClick doesn’t carry information regarding the mouse pointer and coordinates. | Complete |
| WJ-7635 | Bug | Low | Trivial | Treeview node tooltip appears too far on the right. | Complete |
| WJ-7636 | Bug | Low | Trivial | TreeView.BeforeCheck cannot cancel the action | Complete |
| WJ-7637 | Bug | Low | Trivial | When checking/unchecking a tree node it cycles through the undetermined check state | Complete |
| WJ-7638 | Bug | Medium | Minor | TreeView.NodeClick is not fired on a right click. | Complete |
| WJ-7640 | Bug | Medium | Major | Control.Click and Control.MouseClick are not fired for right/middle button clicks. | Complete |
The ToolContainer shrinks to the minimum size enough to hold the child buttons.
The editable widgets (textbox, combobox, ect) have 2 tool containers, one to the left of the inner input and one to the right – in order to hold the tools aligned left or right.
The other non-editable composite widgets (treeview, data grid) have a tool strip at the top that container 2 tool containers. For the grid look under Appearances/Table/Tools. It’s already defined in all the themes.
One way to see what the appearance of an inner widget that is not defined it to click on it in the theme builder and the full path is displayed in the status bar. However in this case there is no preview for the tool container: I will add it somewhere in the preview scripts.
Best,
Luca
The margins are the space relative to other widgets that are managed by one of the layout engines on the client. In the screenshot you can see the top-left margin because the table widget was shifted by the top-left margin, but you cannot see the bottom-right because the inner size of the widget is not altered by the margins, it would show only if there was another inner widget participating in the layout.
For example, if you set the margin of the inner label component in a treenode or a button you can see the inner content rearrange depending on the margin.
To create an inner space use the padding. However, with the table the padding may be used (overridden) by the class if there are controls docked inside the grid.
Basically the margin in theme is not the margin of the control. At the control level, the margin property is managed by the layout engine on the server. The inner components of the widgets are managed by the client layout engines.
HTH
Best,
Luca
Thanks Luca!
Since we are talking about TreeView, I noticed that if a node’s NodeFont is not set explicitly earlier, it is null. Is that normal or a bug? I would expect it to be the same as the TreeView’s Font so that I can check its property values (font Size, Style etc).
Best,
Alex
Hi Tiago,
Sorry for the delay. The icons are white, the issue seems to be the blurring of the straight lines in SVG. It seems that it depends on the multiple of the original size and subpixel drawing. If you change the color to red in the theme you can see that it changes. And if you see the icons on a retina display or zoom in you can see the lines. See zoomed – a bit too big 🙂 – image below, I checked the color of the pixels and it’s white (the tools’s opacity is 0.7):
I will look into the original size of the svg and try to match the scale using a multiple.
Best,
Luca
Hi Luca,
Got you. Better if it can be included in the first release but can be done even after. Just a nice-to-have feature.
Thanks
Hi Cris,
There is a drag-selection mixin in qooxdoo that we can use, but I would wait until we implement column and cell selection. Also, multiple selection supports shift for ranges and ctrl for toggling.
Best,
Luca
Hi Alex,
Thanks, I noticed the same issue with right clicks. They are all fixed now. Will update later on today.
Best,
Luca
Thanks Cris,
I have logged WJ-7641 for the ThemeBuilder and WJ-7642 for the runtime.
Best regards
Frank
Ah, thank you Alex !
Will give it a try.
Hi,
I had seen the same and I had discussed it with Luca, who found the best solution. Instead of giving each combobox as Datasource a the same IList<Item>, give a new BindingSource, the Datasource of which is your IList<item>.
i.e.,
var myList = new List<Item> { new Item { ID = 1, Name = “Name1” }, new Item { ID = 2, Name = “Name2” } };
var C1 = new ComboBox();
C1.ValueMember = “ID”;
C1.DisplayMember = “Name”;
C1.DataSource = new BindingSource(myList, null}; // NOT C1.DataSOurce = myList;
var C2 = new ComboBox();
C2.ValueMember = “ID”;
C2.DisplayMember = “Name”;
C2.DataSource = new BindingSource(myList, null}; // NOT C2.DataSOurce = myList;
Best regards,
Alex
Hi Alex,
for 1) we have logged WJ-7636.
Best regards
Frank
Hi,
Yes, there will be Wisej components for TinyMCE and FCKEditor, but they are not available yet.
We´ll keep you updated.
Best regards
Frank