| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
that you're not creating an image named the same as .'s command,
which refixes 220891, even when the name of the command has been
changed with 'rename'. The error message is better too.
* generic/tkFrame.c (TkToplevelWindowForCommand): Added way of
mapping from command names to tkwins-for-toplevels.
* tests/image.test (image-1.10,image-1.11): Updated to match new
error message and added test for the rename case.
* generic/tclInt.decls: Made TkToplevelWindowForCommand exported
privately.
|
| | |
|
| |
|
|
|
| |
which also requires no documentation changes - the behaviour is now
what you would predict from existing docs (as opposed to a crash!)
|
| |
|
|
|
|
|
|
|
| |
I'm still not quite sure what exactly was going wrong in the bug, but
I suspect the problem might have actually been due to the deletion of
all images while in the midst of creating an image. The restriction
is pretty light when it comes to existing code, since it previously
caused a core dump due to an image typePtr field being set to random
garbage, an indication of over-eager use of free()...
|
| |
|
|
|
|
|
|
| |
* tests/image.test: Added tests for [image inuse] command.
* generic/tkImage.c (Tk_ImageObjCmd): Added [image inuse] command,
which provides a means for programmers to determine if a given
image is in use by any widgets. [RFE: 3327].
|
| | |
|
| | |
|
| |
|
