Hi,
I've encountered a bug with TRMouseMove.
When registered on canvas it doesn't get fired when mouse is over an
element which has any callback registered.
In TRMorph>>rtMouseMoving:
line shape := self shapeWithActionForPositionInPixels: relativePosition.
doesn't respect what kind of event is actually registered to the shape - so
if I register TRMouseClick on a box, TRMouseMove on canvas will not work.
I would expect the event to always get fired for canvas.
Peter
demo:
------------
view := RTView new.
lbl := RTLabel new elementOn: 'position'.
view add: lbl.
badBox := RTBox new size: 50; color: Color red; element.
badBox translateBy: -50 @ -50.
view add: badBox.
goodBox := RTBox new size: 50; color: Color green; element.
goodBox translateBy: 50 @ -50.
view add: goodBox.
badBox
when: TRMouseClick
do: [ ].
view
when:TRMouseMove
do: [ :evt |
lbl shape text: (view canvas camera fromPixelToSpace: evt position)
printString. lbl update.
view signalUpdate ].
view open.
----------------
Hi,
I am trying to work with composite shapes, but I cannot get anything
meaningful to work. I tried the examples, but they do not work either.
For example, RTComposedShapeExample>>exampleInnerShapes does not lay the
nodes.
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi,
I removed both versions of Graph-ET from the Moose and Glamour
configurations. They are still loadable as separate projects.
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi,
I tried to use the RTUmlClassBuilder, but I realized that it is hardcoded
for Pharo classes. Could we work on making it more customizable?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi,
I promised to follow with suggestions for improvement in Roassal.
Currently, my main concern is about the fact that RTNest is not explicit.
Let me explain. I want to debug things related to nesting, and for that I
would like to extend the Elements tab of the view with nesting information
(essentially, I would like a tree). I cannot build this easily, and this
shows me that we have a model problem. This is the side-effect of building
custom tools: if the tool costs too much, you might have to think again
about the model (it's similar with the relationship between tests and
models).
RTNest works at the Trachel level, but it should work at the Roassal level.
I would prefer to have in the RTElement links to the nested elements and
have the nesting not done via a loose Trachel callback but by an explicit
relationship. Alex?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi!
It would be great to be able to add some new menu entry when I right-click on a selected piece of code in a playground.
Can I do that?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi Jan,
Your last commit removed PPContext>>root:, and this made the tests be red.
Could you look at it? :)
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Doru wrote:
>Indeed. For Pharo models, we should ideally run it on allModelPackages.
When would allModelNamespaces be the correct one?
For java projects, I get an off-by-one (1 extra package for
unpackaged classes).
Stephan