Use case defined by ``DrGeoCanvas new``

classic Classic list List threaded Threaded
2 messages Options
HJH
Reply | Threaded
Open this post in threaded view
|

Use case defined by ``DrGeoCanvas new``

HJH
Hello Hilaire

I am looking how the use case defined by

    DrGeoCanvas new

works.


The initialize method is


initialize
        super initialize.
        drgeo := DrGeo applicationToolbarless.
        "We do want it to be on the front"
        self view setProperty: #morphicLayerNumber toValue: 100.
        self view openInWorld.
        self view extent: 400@300.

The view object is a DrGeoWindow object.

I would like to have a DrGeoWindow morph with no toolbars and no scroll wheels.

Does the DrGeo DSL allow for  this or do I need to start changing the code?

It seems that an option could be to set a property after

    self view setProperty: #morphicLayerNumber toValue: 100.

telling the DrGeoWindow object not to add a menu bar and wheels.

Regards
Hannes

HJH
Reply | Threaded
Open this post in threaded view
|

Re: Use case defined by ``DrGeoCanvas new``

HJH
The following text in https://sequencediagram.org/ gives back the
attached sequence diagram


title Creation of a DrGeo sketch: DrGeoCanvas new

User->DrGeoCanvas class:new
DrGeoCanvas class->a DrGeoCanvas:initialize

a DrGeoCanvas->DrGeo class:applicationToolbarless
DrGeo class->app model - drgeo:initialize
a DrGeoCanvas->view = a DrGeoWindow:setProperty: #morphicLayerNumber
toValue: 100.
a DrGeoCanvas->view = a DrGeoWindow:openInWorld
a DrGeoCanvas->view = a DrGeoWindow:extent: 400@300

DrGeoCanvas_new.png (42K) Download Attachment