20 Jul
2010
20 Jul
'10
12:21 p.m.
It does in my image if I drag and drop the node. But if you do not drag a node, the bounds
of the root is not updated.
In any case, the last version should solve the problem. Try it with the code you gave, it
should work.
I added a test for this situation: testInteraction14AddingSubnodeToIncreaseRootSize
Cheers,
Alexandre
On 19 Jul 2010, at 22:33, Johan Fabry wrote:
Hi Alex,
it's still not working for me :-( Test code is below.
- Hover over diamonds do not show 3, 4 or 5
- Clicking on a diamond does nothing.
I tried this in v 506 and 508, same behavior.
view interaction on: MOMouseDown do: [:ann |
view forNode: ann element model do: [
view interaction on: MOMouseDown do: [:ann2|
view forNode: ann2 element model do: [
view shape triangle. view nodes: #(6 7 8 9).]].
view shape diamond. view nodes: #(3 4 5).]].
view nodes: #(1 2)
On 18 Jul 2010, at 15:38, Alexandre Bergel wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi Johan,
Your problem is now solved.
--
Johan Fabry
jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry
PLEIAD Lab - Computer Science Department (DCC) - University of Chile
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev I am still having the same problem in AspectMaps:
If I change the contents of a node with forNode:do: the interaction specified for the new
contents does not work. Below is a test case to run in the easel. Click once on a
rectangle, should open it to show 3 diamonds. (first error: shows 2)
The fact that you have just 2 diamonds is normal. You wrote {3.4.5} in your script, which
is understood as {3.4 . 5} by the Pharo compiler. The first element is 3.4, and the second
is 5.
Click on a diamond, should open it to show 4
triangles. (second error: nothing happens).
Indeed. The reason is that the bitmap cache and the list of elements to lookup when you
click on the screen were not reseted by forNode:do:. The tests I've written for
forNode:do: did not check for this.
Note that you are the only customer of forNode:do:, so you may encounter some bugs that
nobody (even my tests) detected.
I will be highly responsive for the next two/three weeks (half-holidays at my parents).
It is a good moment for you to emit bug report. Afterward, the semester will begin and I
may slow down the pace of programming sessions (hopefully not :)
Regards,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev