Increase resolution of 'Imported Image length' setting

Just a thought. If someone is doing a time-lapse, it's much more efficient to use the "Image Sequence" feature. It can go 1/60 of a second if needed, and is very simple to do, rather than adding each picture individually. As long as the images are named sequentially, such as "Image001.jpg", "Image002.jpg", etc...

Thanks for the suggestion. I have added 2 digits of precision to the "Imported Image Length" preference

Thanks for changing the precision of the "Imported Image Length".
I just tested this new function by changing this value to 0,1 sec.
But after this changing I can't re-open the Preference window to chang it back to another value.
This error appears in the terminal:
-------
on_mnuPreferences_activate called with self.GtkImageMenuItem
Traceback (most recent call last):
  File "/home/jef/openshot/openshot/windows/MainGTK.py", line 1669, in on_mnuPreferences_activate
    preferences.PreferencesMgr(project=self.project, form=self)
  File "/home/jef/openshot/openshot/windows/preferences.py", line 94, in __init__
    self.valImageLength.set_value(float(self.form.settings.general["imported_image_length"]))
ValueError: invalid literal for float(): 0,10
------
It's also not possible to add pictures on the timeline.

The regression has been fixed, and is now in the trunk.

Hi Jef, can you test out the newest version (in the trunk or daily PPA: https://code.launchpad.net/~openshot.developers/+archive/daily) and see if the bug is fixed for you?

Thanks!
-Jonathan

Here how to use this PPA : https://answers.launchpad.net/openshot/+faq/1850

I just did a new installation of the development version like Cenwen explained in his link and it seems to be working again.
Thanks.
But what I don't understand is: what is the difference between always updating to the latest revision with"bzr pull lp:openshot" or with the daily development version?
If I get the latest revision (625, to fix this bug) with "bzr pull lp:openshot" it doesn't work. I should think that I could get it work in this way also.
By the way, how can I check my Local ? Wich commando do I have to use in the terminal?
Thanks for your great work guys.

Strange that bzr pull lp:openshot" doesn't work and the daily development version yes. Normally, it should be.

Silly question, but after pulling the latest code from bazaar, are you changing into the folder where it was downloaded to and starting openshot.py? If you are just running the 'openshot' command it will use the installed version.

Andy, sorry it's hard to tell because I messed up a lot of things with installing Openshot .
In the past I installed the official version with Synaptic and I think I installed the development version (with bazaar) in my home directory.
The commando for the official version is "openshot %F" and I upgrade and start the development version with these commando's in a text file:
#!/bin/sh
cd
cd openshot
bzr pull lp:openshot
cd openshot
python openshot.py

I don't know that this can help you.

I just updated Openshot on another computer with Bazaar to the latest revision (630) and I don't have any problems over there.
So don't be awake tonight to think about the problem on my laptop, I will not :-)

Thanks for the testing help. Looks like this fix is ready to be deployed.