 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | Rules | You are not logged in.
Like Paul, I would prefer next shooting position to be in a highly contrasting bright colour - perhaps white or yellow - rather than having additional cross hairs.
Offline
We already discussed this, and nobody proposed an alternate color scheme (v1 support it). But this is more complicated than unshot/next shoot/done; see:
http://trac.gbiloba.org/papywizard/wiki … lorschemes
Offline
fma38 wrote:
We already discussed this, and nobody proposed an alternate color scheme (v1 support it). But this is more complicated than unshot/next shoot/done; see:
http://trac.gbiloba.org/papywizard/wiki … lorschemes
Never seen that doc. before - very helpful.
Ther appears to be no option to define a fill colour for the 'next position'.?
Offline
No, because the next position state can be unshot, shot-ok, or shot-faild. So, I just use the same colors (grey, green or red), but with lower saturation. If we use another color (yellow, as proposed), we loose this state information... I tend to prefer keeping it, but if you think it is better to use yellow for the next position, whatever the state of that position is (unshot, shot-ok or shot-failed), no problem.
Offline
As we are talking about customizing colors, Qt uses style sheets to define colors, shapes and so. I will add soon the same menu entry as in v1 to load a specific style sheet from the GUI, but it is possible right now to test them using the -stylesheet param frm the command line. For example, under linux (including Nokia/maemo, I think), just run:
$ papywizard.sh -stylesheet <absolute_path_to_your_style_sheet>
I also think it should be possible to do the same from a dos console in windows, except that the starting program is Papywizard.exe (give the absolute path to this exe if you are not in the same dir).
A style sheet can be as simple as:
QLineEdit { background: yellow }
or very complicated. For more informations, have a look at:
http://doc.trolltech.com/4.4/stylesheet.html
Feel free to share your style sheets if you make something nice 
Offline
fma38 wrote:
For more informations, have a look at:
http://doc.trolltech.com/4.4/stylesheet.html
I believe you have discovered the cure for insomnia.
Offline
Ok, I uploaded a new dev. release, 1.9.1, with css support, crosshair cursor for next position, and some improvements on maemo (status bar is now shown, and fullscreen mode is fixed).
If you want a custom css loaded at startup, just put a file named papywizard.css in the config dir.
Offline
how to change PW language on windows pc?
Offline
Internationalisation is not yet implemented in 1.9.x branch... I have to study the Qt's mecanism.
Offline
fma38 wrote:
Ok, I uploaded a new dev. release, 1.9.1, with css support, crosshair cursor for next position, and some improvements on maemo (status bar is now shown, and fullscreen mode is fixed).
If you want a custom css loaded at startup, just put a file named papywizard.css in the config dir.
Nokia N800 latest OS2008 + PW 1.9.1-1
Performance almost unbelievably sluggish when opening the Shooting dialogue window and when running a shoot - I thought the program had hung up after pressing Start, but no it was just slooooooooow!
I really dislike the second crosshair - a real backwards step IMO.
It's very slow to switch from Graphic View to Text View too, and vice versa.
Quite unuseable. 
Last edited by mediavets (2009-02-03 00:03:10)
Offline
Try the 1.9.2 release: I changed the way I display pictures, and reduced the crosshair size for head position: it is now much faster.
Offline
fma38 wrote:
Try the 1.9.2 release: I changed the way I display pictures, and reduced the crosshair size for head position: it is now much faster.
Papywizard 1.9.2-1 on Nokia N800 OS2008
Yes, quite a lot faster - not sure if it is yet as fast as 1.6.x on a 770? Almost useable.
Not too sure I like the small diagonal cross hair, but if that's what it takes to get better performance ...
Rewind/Forward is still rather lagging/sluggish/unresponsive.
I don't like the overlapping circles in Preset Mode, they obscure the view of current/next shooting positions. I prefer the 1.6.x style smaller circles.
Program crashed during a Preset Mode shoot (following a Mosaic Mode shoot) in Simulation Mode.
Of course the virtual keyboard is still not working.
Last edited by mediavets (2009-02-07 14:05:37)
Offline
I think it is still slower than PyGTK. I will have to find another better way to draw the pictures. In fact, what is slow, is when I change the state of pictures (from preview to shot, or next); that's why forward/rewind is slow.
If you don't like the cross, I can use something else, but a small stuff, to avoid PyQt to redraw to much things. I will try to design something better...
About circles, I can switch back to little circles, no problem. I just tried to overlap them to test the click detection.
And I also experience some crashes on Nokia (and some on linux too); I may have some thread issues.
Offline
Ok, have a look at the new release (sorry, I didn't change the name; still 1.9.2). I think it is good, now 
Offline
fma38 wrote:
Ok, have a look at the new release (sorry, I didn't change the name; still 1.9.2). I think it is good, now
Yes, the new current position indicator is OK.
Now much faster as you say.
But....running a simulated Preset Mode shoot with Timer repeat set to 2 it fails to start the second shoot. This seems to be repeatable - it failed in the same way two times running.
Also happens with Mosaic Mode.
Last edited by mediavets (2009-02-07 19:21:15)
Offline
Ok, I found the problem. Thanks for reporting.
So, next step is internationalization, which does not work the same way as PyGTK...
Offline
PW 1.9.3
How do 'Goto Home' and 'Goto initial' differ in their functionality?
Offline
The home position is the (yaw=0, pitch=0) position, as defined with the Home button (inside arrows).
The inital position is the physical position when the head is switched on. This was asked by numz, which wanted to be able to park the head at the end of a shooting.
Offline
I uploaded the 1.9.4 release, with the pulse width parameters... Please, make tests with all your hardwares (Gentle IR, mirror lockup and so).
Offline
fma38 wrote:
I uploaded the 1.9.4 release, with the pulse width parameters... Please, make tests with all your hardwares (Gentle IR, mirror lockup and so).
PW 1.9.4 Windows 2000
It's looking good with the gentled-JUMP, the new scheme prevents unintended repeat triggering with longer exposures.
What I can't yet figure out is what parameter(s) determine the interval between mirror lock-up and shutter trigger.
Last edited by mediavets (2009-02-11 20:45:02)
Offline
Offline
fma38 wrote:
OK - so where/how does the 'pulse low' interval fit in the schematic?
Offline
Read the note at the bottom: it just ensure that there is a minimum delay between 2 pulses. In most cases, it will be OK, because Time value or Stab delay will be much larger than pulse width high. But if you set pulse width high to 0, then time value is used (it appears that there will be an issue for mirror lockup! I will fix it).
I admit that param names are not very good. If you have better ideas...
Offline
Thanks, I think I understand it now.
As I reported it works very well for me with the gentled-Jump and my simple D40; definitely an improvement over the 1.x branch way of doing things because it enables me to overcome/overide the gentled-Jump automatic repeat with long exposures.
I can't think of any better parameter names at present, my aged brain is 'fried' just coping with pulse high/low.
Last edited by mediavets (2009-02-12 12:19:24)
Offline
I uploaded the release 1.9.5 (Nokia/maemo only, but Windows version should come soon), with i18n support, and splashscreen. It should be the last dev. release before the 2.0 one, so please, make deep tests.
I used translation strings from release 1.6.1, so some are still missing. I will ask translators to complete them soon; I just have to collect all usefull informations, as they will have to switch to Qt linguist tool (which is very nice).
Offline
