I set debuglevel to 0 and I still get output in the console? about fancytree

[mar10]

try

$.ui.fancytree.debugLevel = 1; // 0:quiet, 1:info, 2:debug

[pebezo]

Will "debugLevel: 0;" be supported as an init option? (right now it doesn't seem to do anything...)

[mar10]

yes, this would be a good thing

[pnacelli]

Just pulled latest today and "debugLevel: 0" on init option is still outputting, please advise.

Note: seems that it's coming from this: jquery.fancytree.js: line 66

[mar10]

what output do you see? And when (on start up)? Did you clear the browser cache?

[pnacelli]

Hi Martin,

Seeing the output on page load, even after clearing the browser cache, here's a screenshot of the console.

Let me know if you need more info.

[mar10]

Ok, this is from a global debug call ($.ui.fancytree.debug(...)), I will removed this line later.

In general, those global calls cannot be controlled using a tree option. You have to use

$.ui.fancytree.debugLevel = 1; // 0:quiet, 1:info, 2:debug

instead.

[pnacelli]

That worked. Thanks Martin.

[mafar]

@mar10
I have tried

$.ui.fancytree.debugLevel = 1; //
$.ui.fancytree.debugLevel = 0;

and tree option debugLevel: 0 and debugLevel: 1
But i still get ,
<FancytreeNode(#6, 'NAME')> scrollIntoView(): node is invisible.
My tree is hidden in beginning in dropdown

[mar10]

@djangosdk This is a warning and cannot be silenced.
If you feel that there are valid scenarios causing it, please open a seperate issue.

[TimNZ]

@mar10

I added a check in consoleApply() to not output anything if $.ui.fancytree.debugLevel == 0, the warnings were polluting my debug output from my drag* event handlers.

It's not the warnings are invalid, it's being able to control their output when necessary.

[mar10]

@TimNZ This is probably not compatible with the debugLevel property of distinct fancytree instances? (We can discuss this, but please make sure not to mix such modifications with unrelated PRs)