On 20 Jun., 05:58, Yuval Levy goo...@levy.ch wrote:
http://bazaar.launchpad.net/~kfj/+junk/script/view/head:/main/patch5327
sorry I did not add them to the first beta release - was in a way too advanced
state when I saw your message.
I'm glad you did what you did. Well done.
never mind the
Hi all!
I've modified hpi.py, the plugin dispatcher, to provide better
information about exceptions occuring in the python plugins. This
information is printed to the console (sorry, I haven't found a better
way yet) and contains the type of the exception, the text of the error
and a stack
On 19 Jun., 15:55, Yuval Levy goo...@levy.ch wrote:
File /usr/local/share/hugin/data/plugins/crop_cp.py, line 184, in entry
import wx
Much more helpful indeed. that's the bit where wxPython is imported -
crop_cp is the only plugin so far that tries to use wxpython, and I
let it fail
On June 19, 2011 10:32:22 AM kfj wrote:
On 19 Jun., 15:55, Yuval Levy goo...@levy.ch wrote:
I've added two skeleton plugins which do nothing
skeleton or ghosts? I did not find any trace of them in the patch.
sorry, I forgot to issue 'hg add' before 'hg commit'. Here's a new
patch
Hi all!
Prompted by Yuval's recent work on hsi/hpi I have put together a patch
with some minor modifications:
- I've wrapped the C++ type 'vectordouble' as hsi type
'DoubleVector', since some image variable accessors use this type,
notably those for the lens correction parameters.
- I've
On 24 Mai, 05:45, Yuval Levy goo...@levy.ch wrote:
On May 23, 2011 04:08:04 AM kfj wrote:
This probably does the trick:
thank you. getting nearer. let's iterate once more.
hsi/hpi for hugin is optional. It has to be compiled into hugin. This
is done by defining BUILD_HSI=ON in the
On May 23, 2011 04:08:04 AM kfj wrote:
This probably does the trick:
thank you. getting nearer. let's iterate once more.
hsi/hpi for hugin is optional. It has to be compiled into hugin. This
is done by defining BUILD_HSI=ON in the cmake command that sets up the
code generation. Inside
On 20 Mai, 09:11, kfj _...@yahoo.com wrote:
Hi all!
I have updated the README for hsi/hpi and added two plugins to live
with the hugin code base.
I had a look at the data that ended up in the repo and noticed that
parts of the README for hsi were deleted and some text was added. The
section
Hey Kay,
On May 22, 2011 05:05:38 AM kfj wrote:
I had a look at the data that ended up in the repo and noticed that
parts of the README for hsi were deleted and some text was added.
I have read this modified/shortened README and IMHO it is understandable with
room for improvement. I had not
Hi all!
I have updated the README for hsi/hpi and added two plugins to live
with the hugin code base.
All plugins are now in a separate 'plugin' directory off
hugin_script_interface to avoid clutter. Find the changes enclosed in
this patch:
On 19 Mai, 02:39, Yuval Levy goo...@levy.ch wrote:
If we add the scripts that try to import wxPython to the official release,
somebody trying this on an unsupported architecture will get the itch and
scratch it.
I have the niggling feeling that if anyone developing an itch there
would find
I just noticed that python_scripting has been merged into the default
branch yesterday evening. I'd like to take the opportunity and thank
all of you who have been involved in helping the Python interface come
to be. I hope scripting and plugin capability will open up new avenues
for hugin by
On May 19, 2011 03:33:12 AM kfj wrote:
I have the niggling feeling that if anyone developing an itch there
would find scratching dosn't help.
don't worry about that. sometimes, scratching on beton helps redirect the
itch, and there are more solutions than direct scratching, as you found out
On 19 Mai, 14:13, Yuval Levy goo...@levy.ch wrote:
Is there already a canonical location for the scripts? where are they
installed?
There's no need to install them, since hugin's 'run Python script'
dialog is a plain file-select
I beg to differ. I would want to package and
On May 19, 2011 12:03:17 PM kfj wrote:
Maybe it's a bit early to decide on the matter, though,
since the plugin interface is in such an early stage, and what
locations are aptest will become clear once the interface is fleshed
out.
We don't have to reinvent the wheels. there are plenty of
On 20 Mai, 00:54, Yuval Levy goo...@levy.ch wrote:
-DSWIG_EXECUTABLE=/usr/bin/swig2.0
yes, this did the trick. I've updated the wiki. thanks.
keep in mind that self-compiled swig 2.0 will install as /usr/bin/
swig, in which case cmake finds it without help and above switch
probably makes
On 18 Mai, 02:27, Yuval Levy goo...@levy.ch wrote:
already back? the summer has not even started yet!
In summer I usually spend some time at home and some travelling. After
three weeks of mostly living in a tent, with an open fire to heat and
cook, coming back to all the mod cons made for a
On May 18, 2011 07:58:10 AM kfj wrote:
On my Kubuntu system, I can just use wxPython from the
plugin.
Then let's start releasing this. Users of other platforms will find way
to harness similar power for themselves.
We don't have to formally release this - In Python you can just
On 17 Mai, 00:44, Yuval Levy goo...@levy.ch wrote:
Hallo Kay,
how is the wandering in the Alps going?
Fine, thanks. Came back with lots of material, I'm just about done
stitching the panoramas and I also have other stuff to do, but I have
a bit of time for hugin.
- Mac support is still
On May 17, 2011 05:39:19 AM kfj wrote:
how is the wandering in the Alps going?
Fine, thanks. Came back with lots of material
already back? the summer has not even started yet!
- Mac support is still missing
IIRC this is unobtrusive, i.e. if we were to release 2011.2 right after
Hi all!
I've upgraded my system to Kubuntu 11.4. When compiling hugin, apart
from a few minor glitches I noticed that the Python version detection
in CMakeLists.txt in the python_scripting branch's
hugin_script_interface directory wasn't working anymore. I figured out
that this was because the
Hallo Kay,
how is the wandering in the Alps going?
On May 16, 2011 04:53:36 AM kfj wrote:
While at it, I also merged the default branch into python_scripting,
to get python_scripting up to bleeding edge. This was painless and
needed only one trivial manual intervention. So doing the reverse
On March 26, 2011 01:35:56 PM kfj wrote:
I just wish there had been more
success solving issues on 'exotic' systems...
That's beyond your control, don't feel responsible. sometimes it is the
limitations of the 'exotic' system, sometimes it is lack of time, interest,
skill, or a combination
On 26 Mrz., 03:07, Yuval Levy goo...@levy.ch wrote:
On March 23, 2011 11:46:21 am kfj wrote:
When I'm online, I'll
gladly help, but I won't be available continuously, so I feel I
wouldn't make a good mentor.
OK, so not a primary mentor. Still, I suggest you join the mentors when Habi
On March 26, 2011 06:47:59 am kfj wrote:
I feel I have helped already
Indeed you did, thank you very much for your contributions. I respect that it
is your time and you rule. Feel free to chime in any time again, and have a
happy long summer holiday!
Plus, you'll get a Google T-Shirt
On 26 Mrz., 16:37, Yuval Levy goo...@levy.ch wrote:
On March 26, 2011 06:47:59 am kfj wrote:
I can't be bothered to
look at Windows now that I've finally made the move to Linux.
Understand. I recall you sounded quite differently when you first joined this
group. Keep in mind that not
On March 23, 2011 11:46:21 am kfj wrote:
When I'm online, I'll
gladly help, but I won't be available continuously, so I feel I
wouldn't make a good mentor.
OK, so not a primary mentor. Still, I suggest you join the mentors when Habi
sends out the invitation, so you get to give your two cents
On March 21, 2011 05:39:52 am kfj wrote:
On 21 Mrz., 00:40, Bruno Postle br...@postle.net wrote:
I'm not sure that the Windows Hugin package absolutely has to be
statically linked, this may just be the most convenient way to do it
up until now.
if someone with more knowledge of hugin's
Hey Kay
I would suggest that you sign up as a Google Summer of Code mentor when Habi
launches the call for mentors; and I hope we can find a student to work on the
Python interface with your guidance.
I just did:
https://groups.google.com/d/topic/hugin-ptx/qkDQMOMfIXI/discussion.
The call for
Hey Kay
On Mon, Mar 21, 2011 at 10:12, kfj _...@yahoo.com wrote:
On 20 Mrz., 18:56, Yuval Levy goo...@levy.ch wrote:
I would suggest that you sign up as a Google Summer of Code mentor when Habi
launches the call for mentors; and I hope we can find a student to work on
the
Python interface
On 23 Mrz., 11:49, David Haberthür david.haberth...@gmail.com wrote:
Hey Kay
Sorry, I have not read this far in the thread before my reply. Sounds
like a great and interesting summer :) We'll see if a student
nonetheless wants to pick up your pieces (or more like grab the thing
afloat :)
On 20 Mrz., 18:56, Yuval Levy goo...@levy.ch wrote:
I would suggest that you sign up as a Google Summer of Code mentor when Habi
launches the call for mentors; and I hope we can find a student to work on the
Python interface with your guidance.
I understand that this would be helpful, but I
On 21 Mrz., 00:40, Bruno Postle br...@postle.net wrote:
- another issue that's been discussed but not solved is how Python
plugins could be given GUI access. Using wxPython from plugins works
on Linux with Python = 2.7 but not Python 3.X, and not at all on
Windows, quite probably because
On 9 Mrz., 19:37, Bruno Postle br...@postle.net wrote:
On Tue 08-Mar-2011 at 01:41 -0800, kfj wrote:
For me, the Python interface works, and I've hardly modified it in
the last weeks even though I'm using it on a daily basis.
I really would like to use it and see what I can do, but I'm
Kay,
I have Windows XP, without Python installed, and would be willing
to test what happens, but I would need a compiled Windows binary to get
started. I don't have a compiler on my system, so I won't be building
hugin from scratch.
Roger
On 3/20/2011 5:40 AM, kfj wrote:
On 9
On 20 Mrz., 12:22, Roger Goodman rlgood...@cox.net wrote:
I have Windows XP, without Python installed, and would be willing
to test what happens, but I would need a compiled Windows binary to get
started. I don't have a compiler on my system, so I won't be building
hugin from
Hi Kay,
On March 20, 2011 05:40:02 am kfj wrote:
you're not the only one busier with something
else. So, just to remind every one, nothing much is happening with the
Python interface.
I am one of those guilty with not participating in your effort, although I
find it important and laudable.
On Sun 20-Mar-2011 at 02:40 -0700, kfj wrote:
- another issue that's been discussed but not solved is how Python
plugins could be given GUI access. Using wxPython from plugins works
on Linux with Python = 2.7 but not Python 3.X, and not at all on
Windows, quite probably because wxWidgets is
On 8 Mrz., 10:41, kfj _...@yahoo.com wrote:
Hi all!
Noone took notice of my previous post - I suppose very few people are
looking at this thread anyway and Thomas seems to be offline.
And noone looks into the repository. The bundle was pushed some days
ago. But it seems to be easier to
On Tue 08-Mar-2011 at 01:41 -0800, kfj wrote:
For me, the Python interface works, and I've hardly modified it in
the last weeks even though I'm using it on a daily basis. It seems
like the project is slowly fading into oblivion and I'm it's only
user.
I really would like to use it and see
On 9 Mrz., 19:37, Bruno Postle br...@postle.net wrote:
I really would like to use it and see what I can do, but I'm aware
that there are some deadlines approaching and that these have
priority. I suspect that most 'development time' at the moment is
working towards getting the 2011.0.0
On 9 Mrz., 19:26, T. Modes thomas.mo...@gmx.de wrote:
On 8 Mrz., 10:41, kfj _...@yahoo.com wrote:
Hi all!
Noone took notice of my previous post - I suppose very few people are
looking at this thread anyway and Thomas seems to be offline.
And noone looks into the repository. The bundle
Hi all!
Noone took notice of my previous post - I suppose very few people are
looking at this thread anyway and Thomas seems to be offline. Maybe
someone else can pick up my bundle and put it into the SF repo? For
me, the Python interface works, and I've hardly modified it in the
last weeks even
Hi all!
To keep the python_scripting branch in sync with the default branch, I
have merged the default branch into the python_scripting branch,
taking in all changes since the python_scripting branch forked off. I
had to change a very small amount of code to reflect that some headers
have
On 28 Feb., 22:54, Bruno Postle br...@postle.net wrote:
If you are working with HG, you should be able to just pull updates
from the 'default' branch and never worry that your branch is
diverging.
I do worry about 'my' branch diverging. There are some bugs in the
python_scripting branch
On 27 Feb., 00:05, Bruno Postle br...@postle.net wrote:
Sorry, I haven't had time to look into this.
You are missing out. I had hoped that you'd be more interested in my
project, being of the scripting kind yourself. Let me point out that
SWIG, which I use to generate the Python interface, can
On 27 Feb., 09:25, kfj _...@yahoo.com wrote:
Just today I thought about how I could modify it
so that all dependencies to the hsi python module are removed from
hugin itself. This would mean a totally neutral python interface, and
the conversion of C++ pointers into python objects would be
On Sun 27-Feb-2011 at 00:25 -0800, kfj wrote:
You are missing out. I had hoped that you'd be more interested in my
project, being of the scripting kind yourself.
I think it going to be very useful and want to play with it (and even
learn some python), but am very limited with time at the
Hi Kay,
I also changed a few return codes in hpi to avoid potential confusion
about which part produces an error.
Is there some list, what each error code means? So we could add more
meaningfull messages for users/new python developers, if the script or
script interface fails. Currently they
On 26 Feb., 13:30, T. Modes thomas.mo...@gmx.de wrote:
Hi Kay,
I also changed a few return codes in hpi to avoid potential confusion
about which part produces an error.
Is there some list, what each error code means? So we could add more
meaningfull messages for users/new python
On Fri 25-Feb-2011 at 08:33 -0800, kfj wrote:
Yet again, I ask: developers, liaise. Please don't expect of me to do
it all. I'm not a GUI person, really, and I've spent a great deal of
effort getting the backend right. Maybe someone else could look at the
goodies I've stacked up and think of a
Hi group!
I've been busy with the first large Python script using hsi, so there
hasn't been much change to hsi itself in the meantime. Working on my
program I noticed I had omitted Mask.h from the interface, and I
needed masking. So I put it in the interface, together with a template
instatiation
Hi all!
I've added install targets for Linux to CMakeLists.txt which work on
my system and I hope they work on other Linux platforms too.
Thomas, I noticed that you had provided slightly modified 3.py
files which were meant for python 3.X. The only difference I saw was
that these files used
Hi Kay,
Thomas, I noticed that you had provided slightly modified 3.py
files which were meant for python 3.X. The only difference I saw was
that these files used print as a function.
The other difference is the function execfile, as you have fixed.
The patch - and I hope there are no
On 9 Feb., 20:23, T. Modes thomas.mo...@gmx.de wrote:
The other difference is the function execfile, as you have fixed.
I didn't even notice you had changed that - I just took your xxx3.py
files. But I tested on my system with 2.6 and it worked, so it's fine.
Have they taken execfile out of
On 5 Feb., 16:49, Lukáš Jirkovský l.jirkov...@gmail.com wrote:
You may want to do hg pull -u (or hg pull hg up) after commit to
make sure nothing has changed in the repo meanwhile (hehe, I omitted
it in my suggested work flow too). Otherwise you should have no
problems.
So if I do the hg
On 6 February 2011 11:37, kfj _...@yahoo.com wrote:
On 5 Feb., 16:49, Lukáš Jirkovský l.jirkov...@gmail.com wrote:
You may want to do hg pull -u (or hg pull hg up) after commit to
make sure nothing has changed in the repo meanwhile (hehe, I omitted
it in my suggested work flow too).
Hi Kay,
maybe for your use case mercurial queue extention would be a better
alternative instead of fiddling with mercurial commits. So your
changes live in the mercurial queue and you can normal pull the
current state from the main repo.
Concerning line endings: The unix line endings are
On 6 Feb., 13:01, T. Modes thomas.mo...@gmx.de wrote:
Hi Kay,
maybe for your use case mercurial queue extention would be a better
alternative instead of fiddling with mercurial commits. So your
changes live in the mercurial queue and you can normal pull the
current state from the main
Hi Kay,
On 4 Feb., 18:47, kfj _...@yahoo.com wrote:
Hi group!
I've put online another patch for the hugin_scripting branch at my
bazaar repo, plus an updated readme file. This time there wasn't so
much change - it's more consolidation. I did rewrite hpi.py, though,
and hope it'll perform
On 5 Feb., 12:06, T. Modes thomas.mo...@gmx.de wrote:
Commited after some changes.
* Don't misuse configure_file for installing files. Use the install
command instead.
Okay. I'm just now sure about how to go on about the installing on
Linux. So far I'm just keeping the python modules and
On 5 Feb., 12:06, T. Modes thomas.mo...@gmx.de wrote:
Hi Kay,
* Your patch contains a lot a line, where only the line ending were
changed. - Unified
Thomas, when I now look into the hugin_scripting_interface directory,
there is a file 'top_five3.py', which is obviously a modified version
of
Hello Kay,
Sorry I didn't get to this earlier. I must say I'm impressed by your
work. It's a great thing to have scripting interface for quick
prototyping. Unfortunately I can't test it because the computer I use
for development is nonfunctional.
I find it very nice that you and Thomas think
On 5 Feb., 13:10, Lukáš Jirkovský l.jirkov...@gmail.com wrote:
Hello Kay,
Sorry I didn't get to this earlier. I must say I'm impressed by your
work.
Thank you. I feel flattered ;-)
It's a great thing to have scripting interface for quick
prototyping. Unfortunately I can't test it because
If I understand the workings of the cmake code rightly, it will build
the appropriate code for whatever Python it finds libraries for. So if
your system has 3.X, the module should be 3.X as well. SWIG generates
code that is universally compatible. This approach is wise, since on
Linux Python
Hi group!
I've put online another patch for the hugin_scripting branch at my
bazaar repo, plus an updated readme file. This time there wasn't so
much change - it's more consolidation. I did rewrite hpi.py, though,
and hope it'll perform well now, no matter if the plugin is loaded as
a module or
On 29 Jan., 17:45, kfj _...@yahoo.com wrote:
Okay, I can't think of anything else. You'll have to debug it. Once
you have the stack trace, we can have a look at where the actual crash
occurs and take it from there.
Having slept over the matter, I can think of some more things. First
we must
Hi Kay
the versions should match.
Python 2.7 (includes, libs, dll installed with same package, no other
version installed)
Python 2.7 is compiled with MSVC9, as I compile my hugin version
Sorry, I was not successful to provide a backtrace.
When running Hugin with debug the import of the module
On 30 Jan., 11:14, T. Modes thomas.mo...@gmx.de wrote:
Hi Kay
the versions should match.
Python 2.7 (includes, libs, dll installed with same package, no other
version installed)
Python 2.7 is compiled with MSVC9, as I compile my hugin version
Another hope shattered :(
Sorry, I was not
On 30 Jan., 11:14, T. Modes thomas.mo...@gmx.de wrote:
Sorry, I was not successful to provide a backtrace.
When running Hugin with debug the import of the module fails (paths
were modified, so it should find the module). So the script is never
executed.
Must be a Windows problem. Here on
Hi Kay,
the %include window.i did not help.
I propose that as a workaround you change
the declaration and definition of the 'culprit' function to accept a
const SrcPanoImage .
Done. Now it works.
Also added first Python 3 support. It's working here.
Thomas
--
You received this message
On 30 Jan., 15:51, T. Modes thomas.mo...@gmx.de wrote:
I propose that as a workaround you change
the declaration and definition of the 'culprit' function to accept a
const SrcPanoImage .
Done. Now it works.
Excellent. I'm currently thinking about a way to create a test script
to go
On 28 Jan., 20:05, T. Modes thomas.mo...@gmx.de wrote:
There were some more changes in the code necessary:
The MSVC compiler does not support the -o switch. So using
redirection.
I was wondering before why you had used redirection. please excuse my
ignorance of MSVCs workings.
There was
Sorry, I didn't spot the PPS after your signature until I'd sent off
my reply:
PPS: In demo_plugin.py and hpi.py the removed function pano_open is
still used. This needs to be rewritten with the modified syntax.
Another bit which isn't usually used - it was a little test to run
hpi.py from the
On 28 Jan., 21:11, T. Modes thomas.mo...@gmx.de wrote:
PS: In Python I can run import hsi and then modify the panorama
object. But the hugin python interface does not work correctly. It
crashes hugin when running a script that works when running directly
in python.
After more testing I
On 29 Jan., 12:05, T. Modes thomas.mo...@gmx.de wrote:
I get a proper crash of hugin.
I'm using an own script to test, because the print in the demo goes to
nowhere on windows. The scripts contains the following lines:
...
Just some more questions before I ask you to launch the degugger:
On 29 Jan., 12:05, T. Modes thomas.mo...@gmx.de wrote:
def entry ( pano ) :
img=pano.getImage(0)
img.setYaw(90)
pano.setImage(0,img)
It definitely works here from hugin just like this.
When replacing pano.setImage with pano.setSrcImage it works in Hugin.
Maybe
Hi Kay,
Just some more questions before I ask you to launch the degugger:
- did it work before my last patch?
I thought, it worked. But tested again, it did not work before your
last patch.
- are you sure you have a pano open when calling from hugin?
I'm sure, that a pano is open.
- did
On 29 Jan., 16:18, T. Modes thomas.mo...@gmx.de wrote:
Okay, I can't think of anything else. You'll have to debug it. Once
you have the stack trace, we can have a look at where the actual crash
occurs and take it from there.
When I comment out the line with setImage it works. Also only
def
Hi group!
I've continued working on hsi/hpi and feel it's time for another
patch:
http://bazaar.launchpad.net/~kfj/+junk/script/view/head:/main/patch4900.gz
I hope the round number is a good omen!
I've rewritten the CMakeLists.txt, thanks for help from T. Modes and
Kornel Benko for help! I am
Hi Kay,
I've rewritten the CMakeLists.txt, thanks for help from T. Modes and
Kornel Benko for help! I am using a slightly different approach to
precompiling the headers which produce accessor code for image
variables which, I think, is more obvious. The CMakeLists.txt now also
has all
PS: In Python I can run import hsi and then modify the panorama
object. But the hugin python interface does not work correctly. It
crashes hugin when running a script that works when running directly
in python.
After more testing I found the culprit: pano.setImage(0,img)
When calling from
Hi Kay
Your solution absolutely does the trick. I'm no good at cmake, and
seeing what you did with it I'm duly impressed. I feel this is a nice
and clean solution now; it worked on my Ubuntu system, just a tiny
error in CMakeLists.txt - the directive for the gcc preprocessor is -E
and not
On 21 Jan., 18:58, kfj _...@yahoo.com wrote:
I'll put a patch online today or tomorrow and post when I've done so.
The new patch is now online at
http://bazaar.launchpad.net/~kfj/+junk/script/view/head:/main/patch4878.gz
This has the accessor code for class SrcPanoImage and some cosmetic
Hi Kay,
swigpyrun.h is input. It is included by hpi_classes.h which is in turn
included by hpi.cpp. This is why it is needed in the source tree. It's
needed in the making of the hpi object code which is then linked into
libhugin.so, but is irrelevant further down the road and does not
belong
I added also an installer for windows in CMake. The lines for unix are
prepared by comment out because I don't know in which directories the
files should go on unix.
Thomas
--
You received this message because you are subscribed to the Google Groups
Hugin and other free panoramic software
On 22 Jan., 16:05, T. Modes thomas.mo...@gmx.de wrote:
I finally found a solution to automatically create the preprocessed
file and input it into the swig process. So there is no need to fiddle
by hand with the preprocessing and there are not 2 version of the same
file which needs to be in
On 20 Jan., 22:03, T. Modes thomas.mo...@gmx.de wrote:
Thanks for you help.
I finally got it to run. There were some errors in hpi.py (fixed in
repository).
Oops... sorry for the glitch. Most embarassing. Your corrections are
correct ;-) I should have checked more thoroughly...
But you
Hi all!
First of all, thank you all for your assistance! The code is in the SF
repo all right, I made sure by going through a complete pull-up-clone-
branch-compile cycle, and it's looking just fine.
Phew... this was a major piece of work - kept me busy for a good two
weeks, every day all day.
Hi Kay,
continue the accessor issue mentioned in the other thread.
The accessor functions are defined in SrcPanoImage.h, lines 117 - 172
by using macros and inclusion of image_variables.h multiple times.
Thomas
PS: hsi and hpi compiles on windows. Importing the python lib works
also. But when
On 20 Jan., 18:54, T. Modes thomas.mo...@gmx.de wrote:
Hi Kay,
continue the accessor issue mentioned in the other thread.
The accessor functions are defined in SrcPanoImage.h, lines 117 - 172
by using macros and inclusion of image_variables.h multiple times.
Thanks. I'm working on the
On 20 Jan., 21:34, kfj _...@yahoo.com wrote:
On 20 Jan., 18:54, T. Modes thomas.mo...@gmx.de wrote:
Hi Kay,
continue the accessor issue mentioned in the other thread.
The accessor functions are defined in SrcPanoImage.h, lines 117 - 172
by using macros and inclusion of
Hi Kay,
Try and run hugin from the command line and see what the python
interface says why it fails. Most likely it can't load the modules hpi
and hsi because they're not in the module path. Remember hpi.py is not
output, but handcoded and therefore lives in the hsi directory
initially - if
On 17 Jan., 12:59, Pablo d'Angelo pablo.dang...@web.de wrote:
Then you can add your work to this repo and perform hg commit (or hgtk
commit, if you installed tortoisehg (which is quite nice...)). to
commit your changes to the local repo (same as with bzr).
two changesets committed so far,
Hi Kay,
Am 19.01.2011 10:04, schrieb kfj:
hg export 4852:bf77427fe623 4853:9de97bcfd3b2 patch4853
gzip patch4853
I hope this is just what you need and convenient enough to use. Echoes
welcome.
From http://mercurial.selenic.com/wiki/Export, it seems that hg bundle
is the preferred way for
On 16 Jan., 19:39, Pablo d'Angelo pablo.dang...@web.de wrote:
I think once some examples of how to use the interface are available,
even people that could not do any hugin coding can start to contribute.
that is the aim of the plugin interface. And things are looking great
so far; everything
On 16 Jan., 21:33, Roger Goodman rlgood...@cox.net wrote:
Kay,
I read all your posts, but can not help you, as I am not a
programmer at all. From the outside, it looks like you are doing good
work, and creating a useful interface. I say, keep up the good work!
Thanks,
Roger Goodman
On 17 Jan., 12:59, Pablo d'Angelo pablo.dang...@web.de wrote:
Hi Kay,
On 17 Jan., 11:47, kfj _...@yahoo.com wrote:
To get you started, I just created a python_scripting branch in the
main
hugin repository. This branch also contains a Run Python script item
in the
Edit menu, which will
On 17 Jan., 12:59, Pablo d'Angelo pablo.dang...@web.de wrote:
Hi Kay,
Let us know if you hit any roadblocks.
I have it all set up so far, but I don't know how to tell cmake to
compile my cpp file and link it to hugin. The cpp is in hugin.hg/src/
hsi, it should be compiled into an object file
On 17 Jan., 19:54, kfj _...@yahoo.com wrote:
I have it all set up so far, but I don't know how to tell cmake to
compile my cpp file and link it to hugin. The cpp is in hugin.hg/src/
hsi, it should be compiled into an object file and linked with the
rest. In which CMakeLists.txt and where do
1 - 100 of 104 matches
Mail list logo
