Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister

Re: Tk fontCreate, fontNames errors (and fontDelete seems messy)

by converter (Priest)
on Jul 23, 2003 at 05:59 UTC ( #277043=note: print w/replies, xml ) Need Help??

in reply to Tk fontCreate, fontNames errors (and fontDelete seems messy)

When you allocate a new Tk::Font object it makes the newly defined font available to all children of the MainWindow (even if invoked against a child widget, the font is visible to the child's siblings).

You could invoke fontCreate against your MainWindow object reference (i.e. $mw->fontCreate(...);) before calling MainLoop and then use the font when configuring your Toplevel and its child widgets. There's no need to invoke fontCreate more than once.

If you post the relevant bits of your code it should be possible to give more direct advice.


Replies are listed 'Best First'.
Re: Re: Tk fontCreate, fontNames errors (and fontDelete seems messy)
by ff (Hermit) on Jul 23, 2003 at 11:39 UTC
    Ah, progress. Thank you. My mindset had been "no globals" and I was only trying to make resources such as the new font in the screen that needed them.

    As you point out, when a MainWindow invents a font, that font is available to all its children. But when I moved the fontCreate lines into the Toplevel window that was containing the Help button, I got the effect I wanted for the Help button but now that Toplevel (a child of the MainWindow) would not reinvoke because its redefinition of fonts would cause the same error.

    Moving the definition of the fonts all the way back into the first MainWindow solves the problem since the MainWindow is only invoked once, upon initialization of the program. But this need to create a "global" font for some button a few Toplevels down doesn't feel "right"....

      It sounds like you may be allocating this Toplevel each time you want to display it. You might consider allocating the Toplevel once and then mapping/unmapping it as needed. The relevant methods are withdraw and deiconify (see perldoc Tk::Wm), and raise (see perldoc Tk::Widget).

      Here is an example from page 233 of Mastering Perl/Tk:

      use Tk; $mw = MainWindow->new; $mw->title("MainWindow"); $mw->Button(-text => "Toplevel", -command => \&do_Toplevel)->pack(); MainLoop; sub do_Toplevel { if (! Exists($tl)) { $tl = $mw->Toplevel(); $tl->title("Toplevel"); $tl->Button(-text => "Close", -command => sub { $tl->withdraw })->pack; } else { $tl->deiconify(); $tl->raise(); } }

      This would allow you to invoke fontCreate in the same scope as the widget in which the font is intended to be used. The font definition would still be visible to all children of the MainWindow, but you'd have the illusion of scope and maintenance would be a bit easier.

      I've added links to several Perl/Tk-related resources to my home node (with more to come as I find time). Have a look around and you'll probably find a lot of useful information that you didn't know existed.


Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://277043]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others drinking their drinks and smoking their pipes about the Monastery: (4)
As of 2021-04-18 09:24 GMT
Find Nodes?
    Voting Booth?

    No recent polls found