Why is TRCanvas rendered in inspector using RTView?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ TRCanvas>>gtInspectorViewIn: composite <gtInspectorPresentationOrder: -10> composite roassal2 title: 'Canvas'; initializeView: [ RTView new setCanvas: self ] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
shouldn't this be isolated from Roassal layer? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ TRCanvas>>gtInspectorCanvasIn: composite <gtInspectorPresentationOrder: -20> composite morph title: 'Canvas'; morph: [ self buildMorph. self morph ] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Peter
Maybe the zooming...
On Sat, Aug 1, 2015 at 12:32 PM, Peter Uhnák i.uhnak@gmail.com wrote:
Why is TRCanvas rendered in inspector using RTView?
TRCanvas>>gtInspectorViewIn: composite <gtInspectorPresentationOrder: -10> composite roassal2 title: 'Canvas'; initializeView: [ RTView new setCanvas: self ]
shouldn't this be isolated from Roassal layer?
TRCanvas>>gtInspectorCanvasIn: composite <gtInspectorPresentationOrder: -20> composite morph title: 'Canvas'; morph: [ self buildMorph. self morph ]
Peter
Yes. It's was the reuse of the presentation. But, feel free to modify it :). Your suggestion sounds better.
Cheers, Doru
On Sat, Aug 1, 2015 at 1:22 PM, Peter Uhnák i.uhnak@gmail.com wrote:
Maybe the zooming...
On Sat, Aug 1, 2015 at 12:32 PM, Peter Uhnák i.uhnak@gmail.com wrote:
Why is TRCanvas rendered in inspector using RTView?
TRCanvas>>gtInspectorViewIn: composite <gtInspectorPresentationOrder: -10> composite roassal2 title: 'Canvas'; initializeView: [ RTView new setCanvas: self ]
shouldn't this be isolated from Roassal layer?
TRCanvas>>gtInspectorCanvasIn: composite <gtInspectorPresentationOrder: -20> composite morph title: 'Canvas'; morph: [ self buildMorph. self morph ]
Peter
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
+1
Le 1 août 2015 à 10:25, Tudor Girba tudor@tudorgirba.com a écrit :
Yes. It's was the reuse of the presentation. But, feel free to modify it :). Your suggestion sounds better.
Cheers, Doru
On Sat, Aug 1, 2015 at 1:22 PM, Peter Uhnák i.uhnak@gmail.com wrote: Maybe the zooming...
On Sat, Aug 1, 2015 at 12:32 PM, Peter Uhnák i.uhnak@gmail.com wrote: Why is TRCanvas rendered in inspector using RTView?
TRCanvas>>gtInspectorViewIn: composite <gtInspectorPresentationOrder: -10> composite roassal2 title: 'Canvas'; initializeView: [ RTView new setCanvas: self ]
shouldn't this be isolated from Roassal layer?
TRCanvas>>gtInspectorCanvasIn: composite <gtInspectorPresentationOrder: -20> composite morph title: 'Canvas'; morph: [ self buildMorph. self morph ]
Peter
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Yes, I’ve tried your method, and indeed, it removes the zooming and export. Looks like the current implementation is not that bad :-)
Cheers, Alexandre
On Aug 1, 2015, at 8:22 AM, Peter Uhnák i.uhnak@gmail.com wrote:
Maybe the zooming...
On Sat, Aug 1, 2015 at 12:32 PM, Peter Uhnák i.uhnak@gmail.com wrote: Why is TRCanvas rendered in inspector using RTView?
TRCanvas>>gtInspectorViewIn: composite <gtInspectorPresentationOrder: -10> composite roassal2 title: 'Canvas'; initializeView: [ RTView new setCanvas: self ]
shouldn't this be isolated from Roassal layer?
TRCanvas>>gtInspectorCanvasIn: composite <gtInspectorPresentationOrder: -20> composite morph title: 'Canvas'; morph: [ self buildMorph. self morph ]
Peter
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev