Ok, let's start very basic.

Your views start at the root view -- the one you call present on -- and then are heirarchical going down . If you assign a name in the UI editor, you can refer to a subview by name, a but only from it's immediate superview.

Please do the following:. From your button action, call this method on sender.

def print_view(sender): root=sender while root.superview: root=root.superview print('root:', root.name, type(root)) def print_subviews(v, prefix): print(prefix, v.name, type(v)) for sv in v.subviews: print_subviews(v, prefix+'+') print_subviews(root,'')

That will print something like
root UI.View
+view1 UI.view
++button1 ui.Button
++textview1 UI.Textview
+label1 UI.LabelView

Etc. Hopefully this helps explain your view heirarchy.

Note that often people create global variables, or attributes in the root view that point to deep subviews...

root=ui.load_view (....) root.input_box=root['view1']['textview1'] ....

Then you can simply refer to these in your callbacks functions without having to use superview/subview business in your callbacks. If your button takes action on a specific item, that ends up being cleaner. If instead you have 5 buttons using the same action, then you would use sender. Superview

No. It relies on pandas

@ccc
Beauty !

dgelessus - Good catch. I missed the missing space at first when I read the first post.

That is def__init__-ly the problem.

Sorry, I couldn't resist the bad pun.

In my defense, I would have tried to help too, but I just got here.

@b1rchy, I think no, not easily. Thus you might consider e.g. placing a Label inside the Button, and change the text of that. Or go off the deep end and see if there is something in the underlying ObjC UIButton to help you.

I ran into the same problem today. After reading through this thread I realized perhaps it had to do with having both Pythonista 2 and the new Pythonista 3 installed. I uninstalled both and reinstalled 3 and it fixed the problem.

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.

@Darren

You're welcome! Glad to help.

@Swoboderz which extension are you trying to use?

You will note that that chunk if code is using errors, encoding, etc. However:

>>> dir(sys.stdout) ['__class__', '__delattr__', '__dict__', '__dir__', '__doc__', '__eq__', '__format__', '__ge__', '__getattribute__', '__gt__', '__hash__', '__init__', '__le__', '__lt__', '__module__', '__ne__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__weakref__', 'encoding', 'flush', 'isatty', 'write', 'writelines']

notice there is no errors attribute.

So, before calling that code (probably in your script, not in the console, since the streams might be reset when globals get cleared, i forget), just do

sys.stdout.errors ='strict'

or, maybe try a different option, depending on whether you want that bit of code executing or not.

It is all probably moot anyway, since you won't be able to call a c extension that wasnt shipped with pythonista.

@omz Aw darn - Perhaps I can export the list of songs and use an Automator workflow to assemble the playlist instead. Thank you!

@victordomingos There two ways to do this:

You can subclass a TableView and overwrite cell_for_row to create a TableViewCell, add subviews to cell.content_view and then return the cell. There are some hidden options for a TableViewCell. Take a look at this discussion: https://forum.omz-software.com/topic/941/tableviewcell-detail_text_label/3

@hoho9274 since you finally succeeded on a recent version pythonista 3, could you describe how to proceed? Thanks.

Thank you guys! I solved my problem by importing numpy! Thanks again!

Thank you guys! I do have a blank line in my file but now it's gone!

@0x77 I do not know if it helped this time but I often find that creating that minimal script removes all the cruft and allows you to see where the problem(s) lie. Sherlock Holmes once said something similar.

Oh thanks for mentioning the ui.inbackground() stuff - that was the issue !

Actually my code was reloading all the images from a @ui.inbackground section, which is bad design.

Fixed it in order to ensure all is always loaded from the main thread, it works great now !

Sorry for bothering, and thanks for the super fast reply.

OK mido helps.

I just bought the App for the first time (didn't own previous version). Hope this is planned for the near future as it's important for those that need it. I am referring to numpy...