@murphykate Hi, try, if you want, to download this zipped folder inside Pythonista: it has a routine to perform linear programming with scipy (the example solved is the one you find here).

To download this zipped folder run the following script:

#!python2 import urllib url = "https://drive.google.com/uc?export=download&id=1aOdWBReejAk0imtVVHjUMHFui1SmRWVp" filename = "Linear Programming with scipy.zip" urllib.urlretrieve(url, filename)

Extract the zipped folder touching on it: Pythonista will let you to extract it.

Install websocket-client with StaSh.

Then run the script 'main.py' inside the extracted folder.
It should return the same output of the example solved in the above link.

@technoway Hi, I think numpy has no a set of routines for linear programming, but I'm not sure. It is ok for linear algebra but not for any kind optimization (it needs scipy or other tools).

Bye

I uploaded a new version of the code.

The "stop" method was a kludge before, and had some race conditions with the "run" method. While these never happened, they could happen if the timing was just right. Now the method is fully synchronized. All audio control, including stopping audio, is now handled in the "run" thread and the "stop" method became much simpler.

Update: 11/10/2017 - I uploaded again. I did numerous numerical optimizations to make the code more efficient. Most significantly, the rise-fall envelope samples are now cached in a list so they don't have to be recomputed for every tone pulse. I did some polishing of names, methods, and comments. The code is now a bit shorter.

Update: 11/11/2017 - I uploaded again. Now the tone generator uses raised cosine pulse-shaping.

Update: 11/15/2017 - I updated the code yet again yesterday. I realized that the dot and dash tone pulses could be cached for a specific sending speed and a specific tone frequency, and then just used over and over again, as opposed to synthesizing the tone pulses repeatedly. I also synthesized some fixed-interval silences, which depend only on the sending speed. This greatly reduces the loading on the processor, at the expense of using some memory.

Solved my problem.
Added a new method to set the new data to existing widget.

My update view method is the one that uses the new data.

def set_data(self,new_data): self.dia= new_data self.update_view() def refresh_data(self,sender): shelve_file = shelve.open('data') dia = shelve_file['dia'] self.set_data(dia)

David

Hi, thanks for your answer.

I did solve my problem some time ago. In my case the problem was related with a module called holidays.

Somehow this was causing the 'could not load' problem. What I did was to import the module in other place and since thenni never got that message again.

David

See and try sample of @JonB here
It uses attributedText in Objective-C

Sample based on this code

# coding: utf-8 # set attributed text dor existing textview # see JonB code at # https://github.com/jsbain/objc_hacks/blob/master/attribtext2.py import ui from objc_util import * class MyView(ui.View): def __init__(self): self.width = 300 self.height = 300 tv=ui.TextView(flex='wh',frame=self.bounds) tv.delegate = self self.add_subview(tv) tv.begin_editing() UIColor=ObjCClass('UIColor') self.UIred = UIColor.redColor() self.UIfont=ObjCClass('UIFont').fontWithName_size_('Courier',20) #set up objc instance self.tvo=ObjCInstance(tv) def textview_did_change(self, textview): self.stro=ObjCClass('NSMutableAttributedString').alloc().initWithString_( textview.text) i = 0 st = textview.text.find('[',i) l = 1 while st >= 0: self.stro.addAttribute_value_range_('NSBackgroundColor',self.UIred,NSRange(st,l)) self.stro.addAttribute_value_range_(ObjCInstance(c_void_p.in_dll(c,'NSFontAttributeName')),self.UIfont,NSRange(st,l)) self.setAttribs() i = st + 1 st = textview.text.find('[',i) @on_main_thread #apparently this must be called on main thread for textview def setAttribs(self): self.tvo.setAllowsEditingTextAttributes_(True) self.tvo.setAttributedText_(self.stro) v=MyView() v.present('sheet')

It allows you to enter your text and it set the red color for all "[" found in it.

The other approach would be to have your datasource provide a tableviewcell with a highlight applied based on the list of cells to highlight -- you would have to reload to update.

Another option is to create your tableviewcell's once, and store these in your datasource. tableview_cell_for_row would need to return the stored cell. But then you have access to the cell, so can change its contents in realtime. This is not recommended if you have a very large table, since you are wasting memory on cells that are off screen.

@Phuket2 thanks for your reply and comments.
I had played a little with tkinter befor trying pythonista. There, I made a frame called root and placed all of my widgets in the root.
When I start to think of parent child relationships at different levels, things are starting to make sense.
I will read up on superview.

Thank you

No, Pythonista 3 is a separate app, so you need to purchase it again. For a while after Pythonista 3 was released, there was a bundle with Pythonista 2 and 3 in it, which allowed you to get Pythonista 3 at a lower price if you already owned Pythonista 2. This is no longer possible though. (Pythonista 2 is also no longer available for purchase - Pythonista 3 supports both Python 2 and 3, so there's no advantage to buying version 2 instead of 3. If you already own the app, you can still redownload it of course.)

If you do buy Pythonista 3, there is one upgrade-related feature that you can still use. If you go into Pythonista 3's settings, you can enable the "Pythonista 2 Files" option. This shows your Pythonista 2 Script Library as a special folder inside the Pythonista 3 file list, which you can use to easily transfer your files from Pythonista 2 to 3, using the normal "move" button in the file list. You can disable the option later to hide the Pythonista 2 files again (nothing will be deleted of course).

@ccc, just something I need , very nice indeed! I import a game, that for grand-son and daughter, and run it before the background cardimages are shown, meeaning I am on the way for an 4-level game ...
Next try, just using one of the marvallous available games , as next levels ..
.. Topscore files will be used for further interaction ..

Thanks to your example ... Helps a lot 😊 , happy OpaPeter

@procryon , if you look at one of my code examples in this thread you see the delegate being used as @JonB pointed out.
You can see the TextFields Delegate Documentation here

@technoway Python actually has a built-in limit on how deep the Python call stack can go. You can get the current limit with sys.getrecursionlimit() and change it with sys.setrecursionlimit(limit). The default limit is 1000, which is normally enough that you don't overflow the native stack even if you hit the Python recursion limit. In Pythonista that seems to be too much though, if I run an infinitely recursing function with the default limit, Pythonista crashes. With a lower limit (such as 500) I get a Python RecursionError as expected. I have no idea what the size of the native stack is on iOS, but it's probably lower than on Mac.

@Phuket2 Hi, I‘m on the beta program, too, and will have a look at this library! Thanks for the hint! 😃

@AlinMechenici , sorry I can open this in Twitter as I stopped using it. But I think the below link will work for you
https://twitter.com/olemoritz/status/700770989114667009?lang=en

@ihf, I just updated the example to have a copy to clipboard and clear methods and menu items. Not sure they are useful, but good to see how to add menu Items anyway, if you haven't played with them yet.
My example is not as compact looking as it could be, but I try and following the PEP8 style now. Eg, only one import per line, 2 lines after the imports etc.

import ui import clipboard import console class MyConsole(ui.View): def __init__(self, *args, **kwargs): super().__init__(*args, **kwargs) self.tv = None self.make_view() def make_view(self): tv = ui.TextView(frame=self.bounds, flex='wh', font=('Menlo', 24), editable=False, ) self.tv = tv self.add_subview(self.tv) ''' Create 2 ui.ButtonItem to insert into the menubar. ButtonItem's are one of those pesky ui Items that are not subclassed from ui.View Its not a big deal, just good to know they differ from ui.Button. You can see in the docs. Below, I am adding the 2 menu buttons to the right side as it seems to make sense. There is a method left_button_items also. ''' mbtn_clear = ui.ButtonItem(title='Clear', action=self.clear_console, tint_color='red') mbtn_copy = ui.ButtonItem(title='Copy', action=self.copy_console) self.right_button_items = (mbtn_clear, mbtn_copy) def write_line(self, txt): self.tv.text += "{}\n".format(txt) def clear_console(self, sender=None): ''' sender is set to None so sender is not required to call this method. The action from the menu ButtonItem needs to see it there though. But it means you can call this method on the object withouut having to pass a sender. i.e if youwanted to clear the console from your code rather than the menu button action. ie. obj.clear_console() will work. Same goes for the copy_console method below. ''' self.tv.text = "" def copy_console(self, sender=None): clipboard.set(self.tv.text) console.hud_alert('{} characters copied.'.format(len(self.tv.text))) if __name__ == '__main__': f = (0, 0, ui.get_screen_size()[0], ui.get_screen_size()[1]) v = MyConsole(frame=f, name='My Full Sceen Console') v.present(style='', animated=False) for i in range(100): v.write_line('line-{}'.format(i))

@Phuket2 , @ccc Thanks for your inputs. I will try to have a look at it. Much appreciated..

It would be cool if you could add the futurize process (at least steps 0 and 1) which is a much more modern, less distructive approach to the 2to3 conversion that is built into Pythonista.