hugin-0.8.0_rc1 released

[Bruno Postle]

On Sat 09-May-2009 at 02:11 +0200, Guido Kohlmeyer wrote:
>
>> * In constructor GLPreviewFrame glewInit() fails on my machine (return
>> code is 1), but the call to glewInit() in GLViewer::GLViewer returns
>> Ok.
>
>Right, I guess the missing OpenGL context is a problem. The GLViewer
>seems to have a context and glewInit() will work properly. I have to
>analyse it ...

I had a second machine where hugin segfaulted at startup as reported
by others.  It seems that glewInit() can only be called once
depending on how glew is built:

http://glew.sourceforge.net/advanced.html

So I removed the call to glewInit() in GLPreviewFrame.cpp and it
seems to work ok.

I've committed this, though probably there is a better solution.

In particular I still don't have 'difference mode' available in the
fast preview, even though this did work about a month ago.  Both
machines have no hardware acceleration, so the difference mode
worked fine with Mesa software rendering, but now it is disabled.

--
Bruno

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Guido Kohlmeyer]

>
> I had a second machine where hugin segfaulted at startup as reported
> by others.  It seems that glewInit() can only be called once
> depending on how glew is built:
>
> http://glew.sourceforge.net/advanced.html
>
> So I removed the call to glewInit() in GLPreviewFrame.cpp and it
> seems to work ok.
>
> I've committed this, though probably there is a better solution.
>
> In particular I still don't have 'difference mode' available in the
> fast preview, even though this did work about a month ago.  Both
> machines have no hardware acceleration, so the difference mode
> worked fine with Mesa software rendering, but now it is disabled.
>

I applied the approach to check whether the difference feature is
available in OpenGL implementation on the current machine. If so, I add
the difference feature to the drop-down list of the Preview window. Due to
the fact the detection didn't work as expected I can turn clock back and
create the drop-down list as before and leave only a check during runtime
of difference tool. Then hugin won't crash but the difference tool has no
function. Maybe better than a crash ...

Guido


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Bruno Postle]

On Wed 27-May-2009 at 09:40 +0200, Guido Kohlmeyer wrote:
>
>I applied the approach to check whether the difference feature is
>available in OpenGL implementation on the current machine. If so, I add
>the difference feature to the drop-down list of the Preview window. Due to
>the fact the detection didn't work as expected I can turn clock back and
>create the drop-down list as before and leave only a check during runtime
>of difference tool.

Ok, does this need more work? as I'd quite like to push out another
release candidate.

--
Bruno

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Serge Droz]

Hi Bruno,

I did give the RC1 a try on the weekend under
Fedora 10, 64bit.
No Problems encounterted with either assembling stitiching Batch etc.
This obviously implies that it compiled fine.

Thanks for the effort
Serge


Bruno Postle wrote:

> On Wed 27-May-2009 at 09:40 +0200, Guido Kohlmeyer wrote:
>> I applied the approach to check whether the difference feature is
>> available in OpenGL implementation on the current machine. If so, I add
>> the difference feature to the drop-down list of the Preview window. Due to
>> the fact the detection didn't work as expected I can turn clock back and
>> create the drop-down list as before and leave only a check during runtime
>> of difference tool.
>
> Ok, does this need more work? as I'd quite like to push out another
> release candidate.
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Alexandre Prokoudine]

On 27 май, 22:15, Bruno Postle <br...@...> wrote:
> On Wed 27-May-2009 at 09:40 +0200, Guido Kohlmeyer wrote:

> Ok, does this need more work? as I'd quite like to push out another
> release candidate.

On a different note, I have a message from a Russian user that hugin
fails to work on files that are inside directories with cyrillic
names.

It says:

C:\Program\ Files\Hugin\bin\nona -z PACKBITS -r ldr -m TIFF_m -o 1111 -
i 0 C:\DOCUME~1\126C~1\LOCALS~1\Temp\hug16.tmp
ContractViolation:
Precondition violation!
Unable to open file 'C:\Documents and Settings\

Alexandre
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Bruno Postle]

On Mon 01-Jun-2009 at 01:17 -0700, Alexandre Prokoudine wrote:
>
>On a different note, I have a message from a Russian user that hugin
>fails to work on files that are inside directories with cyrillic
>names.

I'm sure this is the same bug there has been for a long time with
Windows and Russian/Czech codepages.  Other languages are fine as
are OS X and Linux:

https://sourceforge.net/tracker/?func=detail&aid=1908349&group_id=77506&atid=550441

>ContractViolation:
>Precondition violation!
>Unable to open file 'C:\Documents and Settings\

--
Bruno

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Harry van der Wolf-3]

I suppose it has to do with the fact that linuxes and OSX use UTF-8 or UTF-16 instead of these "old fashioned" codepages. There is a 6 year old wxwindows "patch" that deals with that same 1251 codepage.
Could it be used to solve this bug?

Harry

2009/6/1 Bruno Postle <bruno@...>

On Mon 01-Jun-2009 at 01:17 -0700, Alexandre Prokoudine wrote:
>
>On a different note, I have a message from a Russian user that hugin
>fails to work on files that are inside directories with cyrillic
>names.

I'm sure this is the same bug there has been for a long time with
Windows and Russian/Czech codepages.  Other languages are fine as
are OS X and Linux:

https://sourceforge.net/tracker/?func=detail&aid=1908349&group_id=77506&atid=550441

>ContractViolation:
>Precondition violation!
>Unable to open file 'C:\Documents and Settings\

--
Bruno

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Harry van der Wolf-3]

Sorry,

Forgot to copy the link in: <http://trac.wxwidgets.org/ticket/5858>

Harry

2009/6/1 Harry van der Wolf <hvdwolf@...>

I suppose it has to do with the fact that linuxes and OSX use UTF-8 or UTF-16 instead of these "old fashioned" codepages. There is a 6 year old wxwindows "patch" that deals with that same 1251 codepage.
Could it be used to solve this bug?

Harry

2009/6/1 Bruno Postle <bruno@...>

On Mon 01-Jun-2009 at 01:17 -0700, Alexandre Prokoudine wrote:
>
>On a different note, I have a message from a Russian user that hugin
>fails to work on files that are inside directories with cyrillic
>names.

I'm sure this is the same bug there has been for a long time with
Windows and Russian/Czech codepages.  Other languages are fine as
are OS X and Linux:

https://sourceforge.net/tracker/?func=detail&aid=1908349&group_id=77506&atid=550441

>ContractViolation:
>Precondition violation!
>Unable to open file 'C:\Documents and Settings\

--
Bruno

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Lukáš Jirkovský]

2009/6/1 Harry van der Wolf <hvdwolf@...>:

> Sorry,
>
> Forgot to copy the link in: <http://trac.wxwidgets.org/ticket/5858>
>
> Harry
>
> 2009/6/1 Harry van der Wolf <hvdwolf@...>
>>
>> I suppose it has to do with the fact that linuxes and OSX use UTF-8 or
>> UTF-16 instead of these "old fashioned" codepages. There is a 6 year old
>> wxwindows "patch" that deals with that same 1251 codepage.
>> Could it be used to solve this bug?
>>
>> Harry
>>
>> 2009/6/1 Bruno Postle <bruno@...>
>>>
>>> On Mon 01-Jun-2009 at 01:17 -0700, Alexandre Prokoudine wrote:
>>> >
>>> >On a different note, I have a message from a Russian user that hugin
>>> >fails to work on files that are inside directories with cyrillic
>>> >names.
>>>
>>> I'm sure this is the same bug there has been for a long time with
>>> Windows and Russian/Czech codepages.  Other languages are fine as
>>> are OS X and Linux:
>>>
>>>
>>> https://sourceforge.net/tracker/?func=detail&aid=1908349&group_id=77506&atid=550441
>>>
>>> >ContractViolation:
>>> >Precondition violation!
>>> >Unable to open file 'C:\Documents and Settings\
>>>
>>> --
>>> Bruno
>>>
>>>
>>
>
>
> >
>

I can see that it has been applied to the trunk, so it's most likely
in all newer wxWidgets. Anyway if I get right it's only fixing the
problem with showing the text in opened window.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Alexandre Prokoudine]

On 2 июн, 10:29, Lukáš Jirkovský <l.jirkov...@...> wrote:
> 2009/6/1 Harry van der Wolf <hvdw...@...>:

> I can see that it has been applied to the trunk, so it's most likely
> in all newer wxWidgets. Anyway if I get right it's only fixing the
> problem with showing the text in opened window.

So there is no way we could have this bug fixed?

Alexandre
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[Harry van der Wolf-3]

2009/6/2 Lukáš Jirkovský <l.jirkovsky@...>

2009/6/1 Harry van der Wolf <hvdwolf@...>:

> Sorry,
>
> Forgot to copy the link in: <http://trac.wxwidgets.org/ticket/5858>
>
> Harry
>
> 2009/6/1 Harry van der Wolf <hvdwolf@...>
>>
>> I suppose it has to do with the fact that linuxes and OSX use UTF-8 or
>> UTF-16 instead of these "old fashioned" codepages. There is a 6 year old
>> wxwindows "patch" that deals with that same 1251 codepage.
>> Could it be used to solve this bug?
>>

I can see that it has been applied to the trunk, so it's most likely
in all newer wxWidgets. Anyway if I get right it's only fixing the
problem with showing the text in opened window.

Sorry that I didn't make myself clear enough. I know it has been applied years ago to the public wxwindows releases and I know it has been done for a very specific purpose, and that purpose is not the same as the issue we are encountering now.
What I meant is: Can this "kind of patch" be used also for the issue we have right now?

Not being a programmer and certainly not into wxwindows, I can't judge it.

Harry

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

[T. Modes]

On 7 Mai, 08:39, "Guido Kohlmeyer" <d...@...> wrote:

> Furthermore theidentifyfeature in OpenGL preview won't work properly on
> Windows. The images are surrounded with a colored line but the buttons to
> enable the images are not colored accordingly. So far as I know this is a
> limitation of wxWidgets on Windows platform. After fixing the OpenGL
> detection bug (see above) I tried to find a way to overcome this
> limitation, cause it's in the same sources. Unfortunately there is no
> simple solution available. I have some ideas to implement a button array
> that is capable to show colored buttons, but this will take some
> development time ... Damn I need some more free time.
>

I modified the fast preview window (svn 3993): I put the toggle
buttons into a panel. This allows to color the panel to get a coloured
border around the button when working with the identify tool. I
activated this colouring only on windows. On linux the whole button is
coloured as it was.
Maybe this new function could also help under Mac: In
GLPreviewFrame::SetImageButtonColour there is a comment that
background color isn't working for toggle button. The same is true for
windows. So somebody on mac could give it a try (you have to modify
the conditional compiler switches in
GLPreviewFrame::SetImageButtonColour and
GLPreviewFrame::CleanButtonColours).

Thomas
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@...
To unsubscribe from this group, send email to hugin-ptx-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---