Home > Archive > PerlTk > February 2008 > Font -12 Helvetica still in cache
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Font -12 Helvetica still in cache
|
|
| Nishant 2008-02-13, 4:22 am |
| Hi all ,
Recently I am coming across an issue where, when I exit from from my
application , it shows -
Font -12 Helvetica still in cache.
The perl version that I am using is 5.8.3 and the Tk version is
804.027.
Pls let me know how to overcome this issue.
Regards
Nishant Sharma
| |
| smallpond 2008-02-13, 10:07 pm |
| On Feb 13, 1:37 am, Nishant <nishant....@gmail.com> wrote:
> Hi all ,
> Recently I am coming across an issue where, when I exit from from my
> application , it shows -
>
> Font -12 Helvetica still in cache.
>
> The perl version that I am using is 5.8.3 and the Tk version is
> 804.027.
>
> Pls let me know how to overcome this issue.
>
> Regards
> Nishant Sharma
When you destroy your top level window Tk destroys all child
windows and all references of any widgets to the fonts, then
it deletes the fonts. This error means that when Tk tried to
delete the font, there were still references to it.
Either you have lost track of widgets which still have
references to this font, or you still have some active
process using it when you exit.
--S
| |
| smallpond 2008-02-13, 10:07 pm |
| On Feb 13, 3:29 pm, smallpond <smallp...@juno.com> wrote:
> On Feb 13, 1:37 am, Nishant <nishant....@gmail.com> wrote:
>
>
>
>
>
>
> When you destroy your top level window Tk destroys all child
> windows and all references of any widgets to the fonts, then
> it deletes the fonts. This error means that when Tk tried to
> delete the font, there were still references to it.
>
> Either you have lost track of widgets which still have
> references to this font, or you still have some active
> process using it when you exit.
> --S
Nishant,
Is this for that threaded app you were working on?
If so, see if waiting for the child threads to exit
fixes the problem.
--S
| |
| Nishant 2008-02-14, 4:24 am |
| On Feb 14, 6:29 am, smallpond <smallp...@juno.com> wrote:
> On Feb 13, 3:29 pm, smallpond <smallp...@juno.com> wrote:
>
>
>
>
>
>
>
>
>
>
>
> Nishant,
> Is this for that threaded app you were working on?
> If so, see if waiting for the child threads to exit
> fixes the problem.
> --S
Hi ,
thanks for your reply.
No , I'm not using threaded app.
So , what is the solution to overcome this and how to figure out if
anything is going wrong ?
Regards
Nishant
|
|
|
|
|