> > So, what is the difference between widgets that have > "ttk__" in their > > name and those that don't? > > They're completely different widgets which use (or at least closely > approximate) the theming of OS-native widgets. The first "t" > stands for "tile" which is the extension that introduced > them. As of Tk 8.5 the tile extension is integrated into the core. > So, both flavors are still referred to as Perl/Tkx?
> > If I want to find help on these widgets, where do I look? > > Under the "Themed Widgets" section of the Tk documentation: > > http://docs.activestate.com/activetcl/8.5/tcl/tk_contents.htm > But, if I look in the documentation, under "ttk_entry", for example, it has "style" under "STANDARD OPTIONS", and if I click on "style" I'm taken to a page where it says "standard options supported by widgets". One of the many "standard options" is "-background" which "Specifies the normal background color to use when displaying the widget". But, that option doesn't work when creating an entry via "new_ttk__entry()". It does work for an entry created via "new_entry()". Is there a list of standard options that aren't supported for a given widget? Mixing ttk and non-ttk widgets is ok? For example one has combo boxes and the other has listboxes, and I want to use both. > > Why is there a difference and what are the advantages and > > disadvantages to one over the other? > > The primary advantage is that it allows you to create Tk apps > that look like native applications. Additionally, there are > some widgets (like > comboboxes) that are only available in ttk. One disadvantage > is that they generally aren't as flexible if you want to set > specific colors/fonts/etc. > When you say "it allows...", are you referring to the themed widgets (ttk)? Not sure what "native applications" means. I'm working in Windows XP and I've yet to see a Perl/Tk, Perl/Tkx, ttk, or whatever the name is, script that looks like a Windows XP app. > > If tkx is supposed to be a thin wrapper over Tcl/Tk, does that mean > > there are different types of entry/button/radio widgets in Tcl/Tk? > > Yup. > > > Any answers to the other questions from the previous post > (#2, 3, 4, > > 7, 8, 9, 10)? > > For 2-4 I don't know offhand. Check the Tk documentation linked above. > > #7 (fill when resizing) is probably the result of not using > -sticky (when using the grid geometry manager) or -expand and > -fill (when using pack). Getting things to resize the way > your used to applications behaving takes practice. > I tried adding -sticky for my subframe, and that just causes a different type of effect. Instead of all the widgets being in the NW corner when resizing, the widgets remain in the center of the window when it is resized. > For #8 (attaching scollbars to a listbox) I recommend using > Tkx::Scrolled. It's a mega-widget (so "yes" to #9) to make it > easy to add scrollbars to anything scrollable. Making a > megawidget isn't all that hard. Tkx includes LabelFrame as a > simple demo. I've made a few and put them on CPAN. > (Tkx::Scrolled is on of them.) > I'll try Tkx::Scrolled. Thanks! I'll also check out LabelFrame. > For #10 (scrollbars after resizing) it sounds like > programmatic resizing isn't triggering the events to update > scrollbars. You may need to do it explicitly. I'd have to dig > through the code to be sure. > Not sure I should have used the term "programmatically". What I would like is that when the window is first created there shouldn't be the window's horizontal and vertical scrollbars, because the window should be sized properly. Depending on the script, sometimes I have scrollbars and other times I don't. > -mjc > -- dss
