You want to use the global keyword inside your functions in order to allow your variable to be modified outside the defining scope.

Actually you think you want globals,but usually they lead to grief, since it can be hard to debug -- for instance when you forget to declare global inside a function, you can read variables defined in external scope but not modify it. So it is easy to get confused.

Consider using a class, then you can store things like that as class instance variables. Then it is never ambiguous which copy of the variable you are modifying.

Add an ImageView to the pyui. Then see https://forum.omz-software.com/topic/4697/pyui-button-image-options/3 for adding custom property with your image file name (which should be saved to the same folder as the pyui)

@ccc, would it not be awesome just to be able to update all the pure-Python stuff that you have installed with one command? I do not know what that command is.

@aidensala and you can do very complex (for me 😀) process, like in this topic

This, or when you're on a connection that is a bit too slow or unreliable for streaming. In that case it's nicer to download a video in the background for a while, so you can watch it uninterrupted afterwards, without having to wait for it to buffer every few minutes.

I agree, it was just a quick sample.
Personnally, I often write my own dialog with images, map view, etc...

is this inside a button action perhaps?

You cannot put a blocking function inside a button action, or other methods that are called on the ui thread. The calls to the form need to be called as @ui.in_background if that is the case.

There may be an issue which I have noticed recently when dealing with for examples the photos picker, that presenting a view while another is closing might lead to issues. yOu might try adding a time.sleep() after wait_modal, since this implies you have another view which is getting closed right before this chunk executes.

It might be helpful to see the entire method, or a complete standalone example that shows the issue.

@ccc , no I was not in any of the beta programs. I found the update worked from the updates page, although from the app's own page when an update is available the button changes from "open" to "update". I was not seeing that from the app's page itself. My only option was "open" and when I opened and went to the settings dialog in Pythonista 3 it clearly said 3.0 and not 3.1 (which it did display after updating from the updates page). Now I have the widget!

I'm afraid you probably won't get many helpful responses here, because discord.py has nothing to do with Pythonista, and because Pythonista isn't the best platform to run a Discord bot on. You'll probably get more help if you ask on a site like Stack Overflow, or on a discussion site for discord.py. Maybe there is a Discord server for discord.py. :)

@JonB I mentioned that as a known issue a while back (first beta, I think), it's still on my todo list.

https://forum.omz-software.com/topic/1907/pythonista-for-python-3-x