You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When changing the fancytree checkbox option, via some event- such us click of the button, the padding is not set right.
I have created a jsfiddle to ilustrate the problem. https://jsfiddle.net/hafasek/9038m2c8/
Any help would be highly appreciated.
The text was updated successfully, but these errors were encountered:
hafasek
changed the title
wide extension - padding is off when checkboxes option are changed
wide extension - padding is off when checkbox option is changed
Oct 18, 2017
ext-wide creates CSS rules in the html header on the fly, taking into account the value of the checkbox: false option.
This is currently done in the treeCreate phase.
A possible solution would be to pull this code into an exported method, so it can be called by developers.
It could then also be called automatically after the checkbox option was modified.
Thank you for a quick reply. I understand your suggestion, but literally have no clue of how to proceed with it. Javascript is not my language of choice.
In treeCreate I found this section, which I believe is to be in the exported method this._local.lineOfs = (1 + (ctx.options.checkbox ? 1 : 0) + (ctx.options.icon === false ? 0 : 1)) * (iconWidth + iconSpacing) + iconSpacing;
Would you be able to direct me to some other extension where some external method is available (and also how to call it afterwards) or just show me some example ideally in jsfiddle?
Ah sorry, the comment was not directed at you specifically, but just an analysis how to fix it (I classified this as bug). It will probably be fixed in the next release.
When changing the fancytree checkbox option, via some event- such us click of the button, the padding is not set right.
I have created a jsfiddle to ilustrate the problem.
https://jsfiddle.net/hafasek/9038m2c8/
Any help would be highly appreciated.
The text was updated successfully, but these errors were encountered: