25 Nov
2013
25 Nov
'13
4:11 p.m.
Looks okay to me. This should not impact the test at all I think.
Maybe you can either produce a change set file (.cs) or send me a new .mcz file?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Nov 25, 2013, at 11:38 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote:
As for me it’s changing
v := (v origin + self step)) corner: (v corner - self step)).
to something like
v := (v origin + (v extent * self step)) corner: (v corner - (v extent * self step)).
And then making step 0.1 instead of 40.
Uko
On 25 Nov 2013, at 15:33, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
You mean providing a value for step? Sure, should
be easy to do. Maybe simply having an instance variable called step and initialising it in
ROZoomOutMove and ROZoomInMove
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Nov 25, 2013, at 11:07 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi,
at the moment RoassalIncrementalZoomMove changes bounds buy a constant size. This means
that the closer we are the more zoom we get and the farther we are the less we can from
out in one step. Can we do this proportionally? It’s not hard to do. I can implement it
myself. The only question is about the concept.
Uko
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev