On July 19, 2011 02:04:52 pm Andreas Metzler wrote:
> The Windowhandling does not seem to have changed.
No, I have not changed the window handling (yet).
The next thing I want to do is to start PTBatcherGUI minimized to the tray.
> Both main window and
> execution details still autohide after a Desktop switch.
I did not notice that, I do not switch Desktop usually. Will try and see what
can be done.
> *However* reading your commit message made me browse the configuration
> menu and to my absolute delight I found that hugin_stitch_project is
> still available as an option.
Yes, when *I* am adding new features I try not to remove existing ones and
leave users the option to fall back on their tried and tested features. There
is always an inherent conflict between new and old. I try not to get into
such conflict. When I do, I try to discuss this first with as many stake
holders as possible. The decision to make PTBatcherGUI the default stitch
engine happened on Hugin-PTX, because the change of default does change the
world to some of us. At some point hugin_stitch_project will be discontinued,
but that's only after users like you are happy to make the switch to
PTBatcherGUI. Sometimes this kind of ideal change management is not possible
- e.g. the effort to maintain the legacy behavior is too big. But it was not
the case with this change.
On July 19, 2011 02:04:52 pm Andreas Metzler wrote:
> The Windowhandling does not seem to have changed.
No, I have not changed the window handling (yet).
The next thing I want to do is to start PTBatcherGUI minimized to the tray.
> Both main window and
> execution details still autohide after a Desktop switch.
I did not notice that, I do not switch Desktop usually. Will try and see what
can be done.
> *However* reading your commit message made me browse the configuration project is
> menu and to my absolute delight I found that hugin_stitch_
> still available as an option.
Yes, when *I* am adding new features I try not to remove existing ones and project will be discontinued,
leave users the option to fall back on their tried and tested features. There
is always an inherent conflict between new and old. I try not to get into
such conflict. When I do, I try to discuss this first with as many stake
holders as possible. The decision to make PTBatcherGUI the default stitch
engine happened on Hugin-PTX, because the change of default does change the
world to some of us. At some point hugin_stitch_
but that's only after users like you are happy to make the switch to
PTBatcherGUI. Sometimes this kind of ideal change management is not possible
- e.g. the effort to maintain the legacy behavior is too big. But it was not
the case with this change.
Yuv