Stretch factor chages rollback

[iko...@earthlink.net]

Hi, ALL,
recentl;y there was a discussion about the changes to
sizer code in regards to some stretch factor refatoring.

My question is: does it fixed in trunk or not?

I have some problems with my code that I compile against the
trunk for about 4-5 month old, and want to test it again if
this is fixed/rolled back.

Thank you.

[Julian Smart]

My (rather strong) preference is for reverting for the time being to
keep compatibility, but Vadim would like to keep it as-is until he has
time to implement a new algorithm which may (I'm not sure) give some of
the same behaviour as 2.8 but respecting minimum size. So you can look
at the current state either as an impasse or deliberate strategy pending
improvements :-)

Meanwhile, I think people who encounter the incompatibility in 2.9 and
can't easily work around it need to stay clear of 2.9 for now.

Regards,

Julian

[iko...@earthlink.net]

Julian,

-----Original Message-----
>From: Julian Smart <jul...@anthemion.co.uk>
>Sent: Nov 7, 2009 12:49 AM
>To: wx-...@googlegroups.com
>Subject: [wx-dev] Re: Stretch factor chages rollback
>
>
>iko...@earthlink.net wrote:
>> Hi, ALL,
>> recentl;y there was a discussion about the changes to
>> sizer code in regards to some stretch factor refatoring.
>>
>> My question is: does it fixed in trunk or not?
>>
>> I have some problems with my code that I compile against the
>> trunk for about 4-5 month old, and want to test it again if
>> this is fixed/rolled back.
>>
>My (rather strong) preference is for reverting for the time being to
>keep compatibility, but Vadim would like to keep it as-is until he has
>time to implement a new algorithm which may (I'm not sure) give some of
>the same behaviour as 2.8 but respecting minimum size. So you can look
>at the current state either as an impasse or deliberate strategy pending
>improvements :-)

Thank you for clarification.
In the meantime I discovered that one of my problems is not related
to this change. I will submit a ticket with this issue based on my
current HEAD snapshot and see if this can be dealt with somehow or
someone can find a workaround.