These are chat archives for ButchersBoy/Dragablz

29th
Jan 2016
Jeremy Stafford
@dasjestyr
Jan 29 2016 06:14

@ButchersBoy (taking it back a week or so) "maybe stick a breakpoint in where the window gets created and post (or look at the call-stack)? The nugget package includes source so you might be able to step back and get some more clues..."

I'm not using any custom window factory; I'm just using it like the example, so I'm not sure where I would stick the break point?

James Willock
@ButchersBoy
Jan 29 2016 07:31
@dasjestyr handle the loaded or activated event in the window and stick a break in there
Ruslan
@ruslanfedoseenko
Jan 29 2016 10:08
@ButchersBoy I mean a header. If user clicks it nothing should happend(i.e no naviagation to content)
Ruslan
@ruslanfedoseenko
Jan 29 2016 10:18
actualy I think I need to disable both. If user is in this tab already and under some circumstances it should be disabled content of tab should not be avaliable.
James Willock
@ButchersBoy
Jan 29 2016 14:21
@ruslanfedoseenko yeah...You need to disable the main content...Cos if the user drag other tabs out, your disabled tab will be visible