tkinter.TclError: image “pyimage3” doesn't exist

后端 未结 4 428
陌清茗
陌清茗 2020-11-27 06:41

I\'m having trouble with a function that shows an image for two seconds on screen, and then is destroyed. When the program runs the functions initial call procedurely works

相关标签:
4条回答
  • 2020-11-27 06:53

    I found the issue so figured I'd answer myself for anyone who has this issue in the future.

    When the wlcm_scrn runs procedurely it is the only window that exists at that point in time, and so it can use tkinter.Tk(). The error arises because the button that calls the function is itself sitting in an active window that is also running as Tkinter.Tk(). So when Python/Tkinter tries to build wlcm_scrn from the button, it's essentially trying to create two windows under root and falling over.

    The solution:

    Changing line...

    wlcm_scrn = tkinter.Tk()
    

    to this...

    wlcm_scrn = tkinter.Toplevel()
    

    ...stops the error, and the image shows.

    I personally am going to have two instances of the function. One called procedurely under Tk(), and one called within the application under TopLevel().

    0 讨论(0)
  • 2020-11-27 06:58

    The PhotoImage method creates an image for the first TK () instance created. Thus, it seems to have solved to inherit TK () instance by replacing TopLevel ().

    This can be solved by specifying the master of the Tk () instance as the option of PhotoImage.

    I think this should be changed.:

    splsh_img = tkinter.PhotoImage(file=file,master=wlcm_scrn)
    
    0 讨论(0)
  • 2020-11-27 07:03

    I had been getting the same error, and the above methods work well to fix it, but i also found that if you aren't going to be changing all of this, then you can restart the kernel (in jupyter notebook) or restart your python interpreter

    And that should make it work the next time. I am not entirely sure how and why this works tho, but it does and is a simple solution for the time being

    0 讨论(0)
  • 2020-11-27 07:04

    Maybe not for this exact case, but for a similar one, I found that the customary

    if __name__ == '__main__':
        wlcm_scrn()  #Call through procedure.
    

    solves the problem as well. This seems to kill the active window and to create a new one each time you re-call the same module.

    0 讨论(0)
提交回复
热议问题