Hi! I finally got it to work! :D I used the adjustSliderPos function from Eric's NestedSlidersPlugin (1) as a template and modified it. I'd tried that before, but it didn't work. It turned out, however, that I had the call to the function at the wrong location. Once I moved it, it worked. The only issue was with repositioning the popup panel on content panel close, which I solved by using a predetermined left position (1442px) since I couldn't figure out how to determine the position of the toolbar command button. However, this turned out to be unnecessary, since I also figured out how to hide everything but the content table (by determining the DOM index of the content panel and hiding everything else). So now everything but the content panel is hidden and the popup panel position is correctly adjusted. Popup problem solved. :) The latest version is up (2).
(1) http://www.TiddlyTools.com/#NestedSlidersPlugin (2) http://infoboxes208test.tiddlyspot.com/ w PS @Mario: Yeah, watching that video again gave me a few ideas where to look :D On Oct 17, 3:11 pm, PMario <[email protected]> wrote: > On 16 Okt., 19:36, whatever <[email protected]> wrote:> Did you check the > correct tiddler (1)? For me, on Win7 in IE, FF, > > yes the right tiddler, but the wrong buttons :) > I didn't see the "infobox info" command line buttons (knowing about > the thread title ;) > > As a user, I wouldn't have a problem if the button is pushed down. For > me the problem is the x coordinate and the content outside the > viewport. > > ===== > having a look with Firebug Inspector, the inner popup is "positon: > relative" to the containing element. > > The containing element is the command line button <ol> which seems to > be created by the toolbar command. The toolbar command functions seem > to calculate the popup position right, if the table wont fit on the > screen. > > Your inner buttons, don't do this calculation. So you'll need to have > a look, how the core does the x/y corrections, and apply them if you > click the inner buttons. ... > > ===== > Since your plugin is allready several hundred lines of code, I'd debug > it in single step mode [1], to actually see, what's going on. It would > help me to learn about your code. But imo it wouldn't help you to find > it yourself. > > I did a "short" video about how to debug TW plugins. > [1]http://www.youtube.com/watch?v=h3NjTLQXWRc > > It is part of a series of videos about TW plugins, I did some time > ago.http://www.youtube.com/playlist?list=PL19F78517CB1EDC08&feature=view_all > > hope this helps > have fun! > mario -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
