prokoudine wrote:
This is because the second one is Scaling: :) I messed it up :)
no problems. should be part of my current patch. now I only hope it
works. when I embarked on this I thought it's just two strings. It
ended up driving me further deep down i18n than I would have ever
wanted.
On Oct 3, 12:59 am, Yuval Levy goo...@levy.ch wrote:
I looked for those strings. I found Loading image: (I did not find
Saving image:, but anyway let's first get it done on a single string).
This is because the second one is Scaling: :) I messed it up :)
Alexandre
On 7 okt, 23:26, Yuval Levy goo...@levy.ch wrote:
Bart van Andel wrote:
It is like letting people tilt beyond nadir/zenith when navigating a
360x180 - fine for the expert who knows what he is doing, but not
helpful for the occasional user.
I don't understand this point. My guess is
Fair enough, though I'd like to remove the crop stuff from the
Stitcher tab at some point, I can't imagine that anyone uses it
there.
Sometimes I have to - because it is impossible to reset a crop border
to 0.
Once you cropped and play around with field of view and different
projections
Yuval Levy schrieb:
J. Schneider wrote:
Can't start system's web browser
top boundary must be smaller than bottom
left boundary must be smaller than right
as new untranslated strings.
The first one is no problem, but can you explain where the other two are
used?
it's when setting the
Bart van Andel wrote:
usability is not universal: different users like
different approaches.
ever visited a usability lab? usability is hard facts and has nothing to
do with likes or dislikes.
user interaction is analyzed and dissected in detail. and the resulting
rules, while depending on
Then tell me where you read that selecting a rectangle should *always*
be done starting from the top left and dragging down right. You're
putting it as if the way you're telling it's supposed to work is the
only way it should ever work, but all programs I'm using or have been
using (including but
On Thu 08-Oct-2009 at 14:00 -0700, Bart van Andel wrote:
Why learn that to create a selection you *must* from the top left
instead of allowing the other options too? What would you consider
easier or more user friendly? I know what I'd prefer.
Having played with it, the original bug is fixed -
Am Tuesday 06 October 2009 schrieb Bruno Postle:
On Mon 05-Oct-2009 at 19:00 -0400, Yuval Levy wrote:
Bruno Postle wrote:
I haven't played with this, but does this really need to generate an
error message?
the fast preview dragging not. but the error can be produced by entering
illegal
On Wed, Oct 07, 2009 at 02:07:12AM -0700, Bart van Andel wrote:
Anyway, instead of a pop up error message box, couldn't we change the
color of the text box (into red for example) and add an exclamation
mark in front with a tooltip text when entering too high / too low
values? Just a
On Mon 05-Oct-2009 at 19:00 -0400, Yuval Levy wrote:
Bruno Postle wrote:
I haven't played with this, but does this really need to generate an
error message?
the fast preview dragging not. but the error can be produced by entering
illegal values on the stitcher tab, where the message is
Bruno Postle wrote:
I'd like to remove the crop stuff from the
Stitcher tab at some point, I can't imagine that anyone uses it
there.
I do use it! I agree it need to go somewhere else, but not removed
completely.
Yuv
--~--~-~--~~~---~--~~
You received this
Hi all, particularly translators.
I have done something that is not very nice IMO: i've just added two new
strings to the release branch (and to trunk, but that's less critical)
after syncing the PO files and calling for translation.
What I can see is
Can't start system's web browser
J. Schneider wrote:
Can't start system's web browser
top boundary must be smaller than bottom
left boundary must be smaller than right
as new untranslated strings.
The first one is no problem, but can you explain where the other two are
used?
it's when setting the crop in the Stitcher
On Mon 05-Oct-2009 at 17:59 -0400, Yuval Levy wrote:
you can see it visually very nicely in the fast preview. before the fix,
dragging the borders of the crop in the fast preview could yield a
negative crop (i.e. you could drag the left crop border over the right
one, or the top over the bottom
Bruno Postle wrote:
On Mon 05-Oct-2009 at 17:59 -0400, Yuval Levy wrote:
you can see it visually very nicely in the fast preview. before the fix,
dragging the borders of the crop in the fast preview could yield a
negative crop (i.e. you could drag the left crop border over the right
one, or
Le 03/10/2009 19:57:16, Yuval Levy a écrit :
Jean-Luc Coulon (f5ibh) wrote:
Sorry, but I want to checkout the related branch but I'm not sure
which
one it is...
is it hugin/2008.4/obsolete_branches/ ?
please work in trunk. I don't know where you get the above path from,
it
does not
Jean-Luc Coulon (f5ibh) wrote:
Le 03/10/2009 19:57:16, Yuval Levy a écrit :
Jean-Luc Coulon (f5ibh) wrote:
Sorry, but I want to checkout the related branch but I'm not sure
which
one it is...
is it hugin/2008.4/obsolete_branches/ ?
please work in trunk. I don't know where you get the
Hi Yuv,
build and install this version of Hugin, to check that it really works
and that I have not broken anything. We need this to be done also in
Windows and OSX, to be sure.
does not compiles on Windows. Compiler complains about not finding
libintl.h.
Also in imagecache.cpp it complains
Hi Thomas,
thanks for the feedback.
T. Modes wrote:
does not compiles on Windows. Compiler complains about not finding
libintl.h.
it's part of gettext. I see that CMake has defines if gettext is found.
I'll boot into Windows later this weekend and have a look.
Also in imagecache.cpp it
Am Samstag 03 Oktober 2009 schrieb Yuval Levy:
Hi Thomas,
thanks for the feedback.
T. Modes wrote:
does not compiles on Windows. Compiler complains about not finding
libintl.h.
it's part of gettext. I see that CMake has defines if gettext is found.
I'll boot into Windows later this
Kornel Benko wrote:
Am Samstag 03 Oktober 2009 schrieb Yuval Levy:
#define _t(String) gettext (String)
sounds the same like with the log2 thing. I'll try to solve it the same
way we solved that.
I think, it is not the same. Here it is defined in wx/intl.h as a macro (not
a function)
Le 01/10/2009 22:45:44, Yuval Levy a écrit :
Hi all, particularly translators.
I have done something that is not very nice IMO: i've just added two
new
strings to the release branch (and to trunk, but that's less critical)
after syncing the PO files and calling for translation.
Sorry, but I
Jean-Luc Coulon (f5ibh) wrote:
Sorry, but I want to checkout the related branch but I'm not sure which
one it is...
is it hugin/2008.4/obsolete_branches/ ?
please work in trunk. I don't know where you get the above path from, it
does not exist.
Yuv
Am Thursday 01 October 2009 schrieb Yuval Levy:
Hi all, particularly translators.
I have done something that is not very nice IMO: i've just added two new
strings to the release branch (and to trunk, but that's less critical)
after syncing the PO files and calling for translation.
The
On 2 окт, 00:45, Yuval Levy goo...@levy.ch wrote:
Hi all, particularly translators.
I have done something that is not very nice IMO: i've just added two new
strings to the release branch (and to trunk, but that's less critical)
after syncing the PO files and calling for translation.
You
Alexandre Prokoudine wrote:
You could do a much worse thing: finally mark Loading image: and
Saving image: messages translatable too :)
OK, I am trying.
DISCLAIMER: newbie at work. I am new to gettext. I don't use non-EN
locale. What I did is like if a legally blind person drives.
I looked
Yuval Levy wrote:
1. add the two new strings to the translation?
since nobody objected, this is what I did. 2009.4.0_beta1 is undergoing
basic tests before uploading.
Yuv
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
28 matches
Mail list logo
