Learned Brother Ken,
Thank you so much for the insight. I code poorly, largely because I borrow code from here and there and crowbar some functionality more by chance than intelligent design. Your teachings are helpful and will probably completely alter my code for the better.
The rather bizarre looking $canvas object was from a progressive overloading of an initially simple object that accumulated more and more functionality. I am, I am ashamed to say, the author of GUIDeFATE; GUIDeFATE results in the production of a GUI, returning a single object that can be used to query/manipulate all the widgets, as well as being able to manipulate the canvas itself. You will immediately get the impression that my failings have already permeated widely in the code affecting multiple sub-modules as I struggled to get a common method for managing multiple different back-end toolkits.
My goal had been to be able to generate a scrolling pane of a predetermined size, placed in a specific location in the window. (hence the need for "place"). This was then to be populated by Tk::Checkbuttons or their equivalent in other toolkits...but if I use relative positioning to place these widgets, they leak out of the Pane widget, rather than remain contained somewhere in the scrollspace of the pane (perhaps unsurprisingly). The vast majority of the examples I have seen on the interweb use ->pack() to produce a list of checkbuttons
But I am grateful for your wisdom. I know I have to do a major rewrite but the fear is great
saif
In reply to Re^2: TK Placing Widgets in a Scrolling Pane
by saiftynet
in thread TK Placing Widgets in a Scrolling Pane
by saiftynet
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |