Well, this is a good new. You can rely on me to test
this and report the result ( i tried myself on CVS
2008/02/19, but i only found src/qsamplerDeviceForm.ui
, src/qsamplerInstrumentForm.ui ,
src/qsamplerOptionsForm.ui ,
src/qsamplerChannelForm.ui and
src/qsamplerChannelStrip.ui having a "margin"
property, and no "topMargin", "leftMargin",
"topMargin" or "bottomMargin" properties. Anyway
Qsampler CVS 2008/02/19 still not compile ).
_but_
taking the words from Rui Nuno Capela this sound like
a 'hack' and i really do not want or ask for a
modification geared only to my specific problem.
Choosing a distro like RHEL comes with drawback, and i
am not waiting for any project assuming it instead of
me. I will insist: solutions are existing. Either
Jsampler, keeping Qsampler on 0.2.1.2 release, or even
only using LSCP script via netcat ( in fact those
scripts are modified once a year, and i always did it
by editing them directly, following your latest
documentation on LSCP ). Upgrading to QT4.3 is also
feasible, and at some point in the futur either Red
Hat or a 'packager' like Dag or Fedora/EPEL will do it
( read: will also maintain the security updates, which
_is_ the main reason for which i don't want to upgrade
to QT4.3, stability is not really involved here as
Linuxsampler is the only project using QT4 on my box.
I am using very few qt programs and they are all
linked to QT3 ).
'Generally' keeping the libraries on the lowest
release is a good choice to allow a project to be used
on 'every' distro. But this simple rule obviously
suffers some exceptions, especially with libraries
coming with poor backward compatibility. In few words:
switching to QT4 was undoubtedly the wise choice,
other projects like qjackctl or qsynth share the same
problems on the same switch, so if you need to follow
the latest release from Trolltech/Nokia, go for it and
don't take care to the rest, QT4 will stabilize
sometime and then a merge to the present release of
Qsampler will be easy, at least easier.
I really mean it, i will obviously appreciate a hack,
but i am perfectly happy with the answer of Christian
Schoenebeck: i can't compile the latest Qsampler
because i need QT4.3, this is clear and simple. So my
only advise on the topic is: take just care to make
the best choice for your project, i know nothing about
C++ and QT, so i can't help you to evaluate if a hack
will be a serious drawback in one year or two, except
saying that 'generally' a hack is not a good idea ;-)
Best regards
--- Rui Nuno Capela <[EMAIL PROTECTED]> wrote:
> hilare wrote:
> >
> > 2/ investigating the workaround given by Rui Nuno
> > Capela. A good idea, but how long this will stand
> for
> > ( i mean what about QT 4.4, 4.5, ... )
> >
>
> believe me, this is THE solution. in fact it's just
> a matter of time to
> make it officially through qsampler code base ;)
>
>
> >
> > --- Rui Nuno Capela <[EMAIL PROTECTED]> wrote:
> >
> >> there's one "simple" way to make it build on qt4
> <
> >> 4.3: edit the .ui by hand (not using designer)
> and
> >> colapse "topMargin","leftMargin","topMargin" and
> >> "bottomMargin" properties into one single
> "margin".
> >>
> >> it's a damn fault of the trolls (now nokian?) in
> not
> >> making qt designer backward compatible, specially
> on
> >> silly changes that just don't stack
> >>
>
> cheers
> --
> rncbc aka Rui Nuno Capela
> [EMAIL PROTECTED]
>
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Linuxsampler-devel mailing list
Linuxsampler-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
