1. Home
2. Pythonista

Pythonista

• 

  fig.canvas.flush_events() -> NotImplementedError
  posted

  2
  Posts
  196
  Views

  JonB

  Matplotlob on pythonista has some limitations, since it is not based on gtk, etc. So just the image back end.

  I have an experimental pythonista back end, which allows interactive plots.

  https://github.com/jsbain/backend_pythonista

• 

  Hiding extended keyboard
  posted

  4
  Posts
  499
  Views

  rugby_dragon

  Hi

  I would agree on the new 11” iPad Pro with apple Smart Keyboard its unusable. Can this be fixed

• 

  Rank Beginner on Pythonista
  posted

  4
  Posts
  285
  Views

  TomD

  Thanks all. Making progress.........

• 

  Why my “print” function is ptinting the triplle of values of variable “g” and “ag” instead of only 1 value for ag and 3 for ag?
  print function • posted

  4
  Posts
  246
  Views

  Drizzel

  import numpy as np import sys import motion import matplotlib.pyplot as plt from time import sleep import console g=0; ag=0; data=0; data_ag=0; del g del ag del data del data_ag fs=100; duration=5; def main(): console.alert('Motion Plot', 'When you tap Continue, accelerometer (motion) data will be recorded for 5 seconds.', 'Continue') motion.start_updates() sleep(0.2) print('Capturing motion data...') num_samples = fs*duration; data = [] data_ag = [] for i in range(num_samples): sleep(1/fs) ag=motion.get_user_acceleration(); g = motion.get_gravity(); #a=motion.get_gravity() #motion.get_attitude() #motion.get_magnetic_field() data.append(g); data_ag.append(ag); motion.stop_updates() print('Capture finished, plotting...') x_values = [x/fs for x in range(num_samples)] for i, color, label in zip(range(3), 'rgb', 'XYZ'): plt.plot(x_values, [g[i] for g in data], color, label=label, lw=2) szg=sys.getsizeof(g) print(szg) print(g) print(ag) print(type(data[1])) plt.grid(True) plt.xlabel('t') plt.ylabel('G') plt.gca().set_ylim([-1.0, 1.0]) plt.legend() plt.show() main()
• 

  Text input in a <Scene> based Game
  posted

  10
  Posts
  572
  Views

  FarmerPaco

  Here is a sample of using ui.textfield for input in scene

  Here is a pic of textfield receiving input in Scene.

• 

  File handling CSV files and TXT files within Phytonista
  posted

  14
  Posts
  451
  Views

  cvp

  @jokiehints 🍾👍

• 

  Analyser and R for IOS
  posted

  19
  Posts
  4078
  Views

  JonB

  Analyzer and Juno are two apps that advertise support for scipy/pandas and the like. If that is a priority for you, I'd suggest you invest in one of those apps.

• 

  Module runs in stash but not on console
  console stash • posted

  11
  Posts
  364
  Views

  JonB

  no problem. for modules that define a main like that, that will work. in some cases, a module might have

  if __name__=='__main__': do_stuff()

  in which case, run_py is the way to go (python -m actually uses run_py under the hood)

• 

  Add photo to .pyui file
  pythonista 3 python 3 ui.image • posted

  2
  Posts
  326
  Views

  JonB

  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)

• 

  Possible to run full apps? (Want to run Zim.)
  posted

  3
  Posts
  425
  Views

  ellie_ff1493

  zim made for keyboard and mouse, if you do somehow get it working its not going to work with a screen, look at the scene module

• 

  Using argv
  posted

  2
  Posts
  247
  Views

  JasonN

  Ah, I figured it out.

• 

  Keyboard frame change view methods oddness...
  textfield keyboard textview • posted

  12
  Posts
  551
  Views

  mikael

  @shinyformica, gist seems good if it is clear that it is not going to need many revisions, issues, a Readme or collaboration. Otherwise, a git repo is not that much more work.

• 

  Problem when pip installing matplotlip
  posted

  6
  Posts
  780
  Views

  JonB

  Matplotlib comes preinstalled. You cannot update it.

• 

  Read out accelerometer and gyroscope from movement service (TI sensortag CC2650)
  posted

  14
  Posts
  2150
  Views

  ProgrammingGo

  Hi, I tried out to set up 16g range to the accelerometer, activating only accelerometer with range of 16g like the following: bytes([0b00111000, 0b00000011] and the to convert the raw data I used the formula stated in the wiki of TI: http://processors.wiki.ti.com/index.php/CC2650_SensorTag_User's_Guide#Movement_Sensor

  ---> v = (raw(data * 1.0) / (32768/16) for every axes and the output seems to be not right because in static position I get the following values for x, y, z: 1.9414, 0.0786, 0.225. Normally the first value(x) should be around 0.981. When I am changing the configuration to bytes([0b00111000, 0b00000010] which should be 8G range and use the following formula: v = (raw(data * 1.0) / (32768/8) then seems to be correct and in static position I have following values: 0.920 , 0.005, 0.200. Do you know what is the problem? I checked the formula and the settings but it should be right. The problem is well known, but not solved , See here: https://evothings.com/forum/viewtopic.php?t=1875

  https://github.com/sandeepmistry/node-sensortag/issues/62

• 

  using cb library to read out sensortag uuid
  posted

  9
  Posts
  691
  Views

  ProgrammingGo

  @JonB yes you are right, the alternative is quite nice and there is this Serial number string, but when Iam reading it out it says N.A ---> not available and it seems to be the same for every sensor

• 

  Removing current clipping
  posted

  3
  Posts
  289
  Views

  xxao

  Thanks, that works. Unfortunately I cannot use the "with..." directly but storing the state and using state.enter() and state.exit() does exactly what I need. Would be nicer to use something like state.save() and state.restore() but I have not found anything like this.

  Thanks again.

• 

  Odd variable bug with scene
  posted

  4
  Posts
  389
  Views

  WalterJ

  Ok, thanks for the refresher on how Python manages member variables or data attributes. I haven't done a lot of python OOP yet.

  So it sounds like scene's internal variables are in the same namespace as the variables we create to perform our animation, and that makes sense now that I've thought about it. I don't know why it surprised me so much. I did read a fair amount of documentation before writing my code, I guess it would have been nice if there had been a mention of avoiding scene's internal variables when introducing scene.

  For the benefit of anyone running across this after making the same mistakes here is the fixed version:

  from scene import * class MyScene (Scene): # note any variables declared here are class variables (shared by all copies of the class # Also avoid Scene's internal variables like t, dt, etc. setup(self): self.my_t = 0.1 #this is an instance variable, each copy of the class would get it's own def draw(self): print(self.my_t) run(MyScene())
• 

  Openpyxl problem
  posted

  4
  Posts
  2056
  Views

  cronywalls

  This error statement TypeError: 'module' object is not callable is raised as you are being confused about the Class name and Module name. The problem is in the import line . You are importing a module, not a class. This happend because the module name and class name have the same name .

  If you have a class "MyClass" in a file called "MyClass.py" , then you should import :

  from MyClass import MyClass

  In Python , a script is a module, whose name is determined by the filename . So when you start out your file MyClass.py with import MyClass you are creating a loop in the module structure.

• 

  Two Questions: Same Issue : File Management
  posted

  11
  Posts
  821
  Views

  adrius42

  @JonB have finally sussed the some of the mysteryies of Stash, not least how to run it!
  How would I have discovered the existence of the -la extension to ls without your kind help?
  I have tried ‘man ls’ with no joy...

• 

  Changing button shape using up.Path
  posted

  11
  Posts
  688
  Views

  RoninSage

  @brumm thanks, just enough info for me to figure it out.