September 2012 - Pharo-users

Re: [Pharo-users] Get the point of Intersection for Morphs

by irfankhan1

I solved this intersection of points using this link http://paulbourke.net/geometry/2circle/ <http://paulbourke.net/geometry/2circle/> Here is my workspace code |b b1 r r1 r2 d d1| b1:= CircleAnimeMorph new. b1 center: 100@100. b1 openInWorld. b:= CircleAnimeMorph new. b openInWorld. d:= b1 center dist: b center. "distance between 2 circles" r:=b1 bounds width /2. "radius of first circle" r1:=b bounds width/2. "radius of second Circle" r2:=r + r1 . (d )< (r2) ifTrue: [| a h mid c c1 myPen h1 h2 mx my mc mc1| a := (r squared - r1 squared + d squared) / (2 * d). h := (r squared - a squared) sqrt. h1:= b center y - b1 center y. h2:= b center x - b1 center x. mx:=a * (b center x - b1 center x)/d. my:=a* (b center y - b1 center y)/d. mid := ((mx)+(b1 center x) @ (b1 center y )+(my) ) " calculates mid point between 2 intersecting circles (p2)" { mc:=(h * h1)/d. mc1:=(h * h2)/d. c:=(mid x + mc )@ (mid y - mc1 )."Actual Intersecting points" c1:=(mid x -mc) @ (mid y + mc1 )."Actual Intersecting points" Transcript show: (c); show: (c1); cr}. myPen := Pen new. myPen color: Color red. myPen putDotOfDiameter: 5 at: mid. myPen putDotOfDiameter: 5 at: c1. myPen putDotOfDiameter: 5 at: c.]. Can any one help me make this a methods ,I wanna make this a intersection method which will do all this when i say b1 intersection:b. should do all of this and draw colored dots at intersecting points -- View this message in context: http://forum.world.st/Get-the-point-of-Intersection-for-Morphs-tp4646066p46… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 23, 2012

Re: [Pharo-users] Problems with a Morph that accepts File Dropping in Pharo 1.3+

by StÃ©phane Ducasse

What is really strange is that the event location is always too large. I put the dropZone on 0@0 - 200@200 and I drop a file on it and the event location is 15@800â¦. I traced that up to HandMorphâ¦processEvents and this is event in the evtBuf of the vm. Stef dispatchDefault: anEvent with: aMorph "Dispatch the given event. The event will be passed to the front-most visible submorph that contains the position wrt. to the event." | localEvt index child morphs inside | "See if we're fully outside aMorphs bounds" (anEvent class = DropFilesEvent ) and: [(aMorph class = DropZone) ifTrue: [self halt]]. (aMorph fullBounds containsPoint: anEvent position) ifFalse:[^#rejected]. "outside" "Traverse children" index := 1. morphs := aMorph submorphs. inside := false. [index <= morphs size] whileTrue:[ child := morphs at: index. localEvt := anEvent transformedBy: (child transformedFrom: aMorph). (child processEvent: localEvt using: self) == #rejected ifFalse:[ "Not rejected. The event was in some submorph of the receiver" inside := true. localEvt wasHandled ifTrue:[anEvent copyHandlerState: localEvt]. index := morphs size. "break" ]. index := index + 1. ]. "Check for being inside the receiver" inside ifFalse:[inside := aMorph containsPoint: anEvent position event: anEvent]. inside ifTrue:[^aMorph handleEvent: anEvent]. ^#rejected

Sept. 23, 2012

Re: [Pharo-users] Problems with a Morph that accepts File Dropping in Pharo 1.3+

by StÃ©phane Ducasse

but this is the same :) Slowly debugging step by step the process it seems that the (aMorph fullBounds containsPoint: anEvent position) ifFalse:[^#rejected]. "outside" pass in the false path in 20 and true path in 1.1 May be localEvt := anEvent transformedBy: (child transformedFrom: aMorph). the transformation changed the position. Stef

Sept. 23, 2012

Re: [Pharo-users] Problems with a Morph that accepts File Dropping in Pharo 1.3+

by StÃ©phane Ducasse

On Sep 23, 2012, at 4:35 PM, Helene Bilbo wrote: > StÃ©phane Ducasse wrote >> I tried the same on 2.0 and this is in both cases the PasteUpMorph that >> get it. So. >> >> ok in 1.1-11411 >> I got your halt. :) > > So, you found my problem :) not really so far the code is the same. dispatchDefault: anEvent with: aMorph Now this method is used continuously. I put an halt inside to get a debugger when the drop event is managed dispatchDefault: anEvent with: aMorph "Dispatch the given event. The event will be passed to the front-most visible submorph that contains the position wrt. to the event." | localEvt index child morphs inside | "See if we're fully outside aMorphs bounds" (aMorph fullBounds containsPoint: anEvent position) ifFalse:[^#rejected]. "outside" "Traverse children" index := 1. morphs := aMorph submorphs. inside := false. [index <= morphs size] whileTrue:[ child := morphs at: index. localEvt := anEvent transformedBy: (child transformedFrom: aMorph). (child processEvent: localEvt using: self) == #rejected ifFalse:[ "Not rejected. The event was in some submorph of the receiver" inside := true. localEvt wasHandled ifTrue:[anEvent copyHandlerState: localEvt]. index := morphs size. "break" ]. index := index + 1. ]. "Check for being inside the receiver" anEvent class = DropFilesEvent ifTrue: [self halt.]. inside ifFalse:[inside := aMorph containsPoint: anEvent position event: anEvent]. inside ifTrue:[^aMorph handleEvent: anEvent]. ^#rejected Now in Pharo 2.0 dispatchEvent: anEvent with: aMorph "Dispatch the given event for a morph that has chosen the receiver to dispatch its events. The method implements a shortcut for repeated dispatches of events using the same dispatcher." anEvent type == lastType ifTrue:[^self perform: lastDispatch with: anEvent with: aMorph]. "Otherwise classify" lastType := anEvent type. anEvent isMouse ifTrue:[ anEvent isMouseDown ifTrue:[ lastDispatch := #dispatchMouseDown:with:. ^self dispatchMouseDown: anEvent with: aMorph]]. anEvent type == #dropEvent ifTrue:[ lastDispatch := #dispatchDropEvent:with:. ^self dispatchDropEvent: anEvent with: aMorph]. anEvent isWindowEvent ifTrue:[ lastDispatch := #dispatchWindowEvent:with:. ^self dispatchWindowEvent: anEvent with: aMorph]. lastDispatch := #dispatchDefault:with:. ^self dispatchDefault: anEvent with: aMorph the last line is executed while in 1.1 dispatchEvent: anEvent with: aMorph "Dispatch the given event for a morph that has chosen the receiver to dispatch its events. The method implements a shortcut for repeated dispatches of events using the same dispatcher." anEvent type == lastType ifTrue:[^self perform: lastDispatch with: anEvent with: aMorph]. it stopped in this branch. "Otherwise classify" lastType := anEvent type. anEvent isMouse ifTrue:[ anEvent isMouseDown ifTrue:[ lastDispatch := #dispatchMouseDown:with:. ^self dispatchMouseDown: anEvent with: aMorph]]. anEvent type == #dropEvent ifTrue:[ lastDispatch := #dispatchDropEvent:with:. ^self dispatchDropEvent: anEvent with: aMorph]. anEvent isWindowEvent ifTrue:[ lastDispatch := #dispatchWindowEvent:with:. ^self dispatchWindowEvent: anEvent with: aMorph]. lastDispatch := #dispatchDefault:with:. ^self dispatchDefault: anEvent with: aMorph > > Any idea, what i can do about it? > > It is a pity (and a bug - as when you make the custom DropZone morph bigger, > some parts of it handle the dropped file, while some other parts of it, pass > it on to the PasteUpMorph) that it does no longer work this way, and i could > not find any reason for it.. > > > > -- > View this message in context: http://forum.world.st/Problems-with-a-Morph-that-accepts-File-Dropping-in-P… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Sept. 23, 2012

Re: [Pharo-users] Problems with a Morph that accepts File Dropping in Pharo 1.3+

by StÃ©phane Ducasse

I will try to have a look. Now putting a halt in such method can block everything :) Stef On Sep 23, 2012, at 4:35 PM, Helene Bilbo wrote: > StÃ©phane Ducasse wrote >> I tried the same on 2.0 and this is in both cases the PasteUpMorph that >> get it. So. >> >> ok in 1.1-11411 >> I got your halt. :) > > So, you found my problem :) > > Any idea, what i can do about it? > > It is a pity (and a bug - as when you make the custom DropZone morph bigger, > some parts of it handle the dropped file, while some other parts of it, pass > it on to the PasteUpMorph) that it does no longer work this way, and i could > not find any reason for it.. > > > > -- > View this message in context: http://forum.world.st/Problems-with-a-Morph-that-accepts-File-Dropping-in-P… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Sept. 23, 2012

Re: [Pharo-users] Problems with a Morph that accepts File Dropping in Pharo 1.3+

by Helene Bilbo

StÃ©phane Ducasse wrote > I tried the same on 2.0 and this is in both cases the PasteUpMorph that > get it. So. > > ok in 1.1-11411 > I got your halt. :) So, you found my problem :) Any idea, what i can do about it? It is a pity (and a bug - as when you make the custom DropZone morph bigger, some parts of it handle the dropped file, while some other parts of it, pass it on to the PasteUpMorph) that it does no longer work this way, and i could not find any reason for it.. -- View this message in context: http://forum.world.st/Problems-with-a-Morph-that-accepts-File-Dropping-in-P… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 23, 2012

Re: [Pharo-users] Problems with a Morph that accepts File Dropping in Pharo 1.3+

by StÃ©phane Ducasse

> StÃ©phane Ducasse wrote >> which kind of files are you dropping because dropping a .st file does the >> same on 2.0 and 1.2 > > Yes, that's the problem. It's PasteUpMorph that handles all the dropped > files. I want to make a custom Morph, DropZone, that handles dropped files. > Of course i could alter PasteUpMorph, but there is a functionality that > worked in 1.2 and works in Squeak, that ceased to work in 1.3+, that allowed > to make morphs that handle dropped files. Do you have a scenario that works in 1.2 because I got exactly the same behavior with 1.2 and 2.0? When I drop a txt file I get a workspace in both version. When do you get your halt open. in 1.2 I put an halt into Morph>>handleDropFiles: anEvent "Handle a drop from the OS." self halt. anEvent wasHandled ifTrue:[^self]. "not interested" (self wantsDropFiles: anEvent) ifFalse:[^self]. anEvent wasHandled: true. self dropFiles: anEvent. I tried the same on 2.0 and this is in both cases the PasteUpMorph that get it. So. ok in 1.1-11411 I got your halt. :) MorphicEventDispatcher>>dispatchDefault: anEvent with: aMorph "Dispatch the given event. The event will be passed to the front-most visible submorph that contains the position wrt. to the event." | localEvt index child morphs inside | "See if we're fully outside aMorphs bounds" (aMorph fullBounds containsPoint: anEvent position) ifFalse:[^#rejected]. "outside" "Traverse children" index := 1. morphs := aMorph submorphs. inside := false. [index <= morphs size] whileTrue:[ child := morphs at: index. localEvt := anEvent transformedBy: (child transformedFrom: aMorph). (child processEvent: localEvt using: self) == #rejected ifFalse:[ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ "Not rejected. The event was in some submorph of the receiver" inside := true. localEvt wasHandled ifTrue:[anEvent copyHandlerState: localEvt]. index := morphs size. "break" ]. index := index + 1. ]. "Check for being inside the receiver" inside ifFalse:[inside := aMorph containsPoint: anEvent position event: anEvent]. inside ifTrue:[^aMorph handleEvent: anEvent]. ^#rejected > Background: I made an application for the psychology department of a > university that parses Tobii eyetracker files (with PetitParser, which works > AMAZINGLY WELL!) and does all sorts of calculations with them. I want to > provide a nice interface, that allows users to drop the eyetracker files on > a Pharo window to start the file processing. > > > > -- > View this message in context: http://forum.world.st/Problems-with-a-Morph-that-accepts-File-Dropping-in-P… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Sept. 23, 2012

Re: [Pharo-users] Problems with a Morph that accepts File Dropping in Pharo 1.3+

by Helene Bilbo

StÃ©phane Ducasse wrote > which kind of files are you dropping because dropping a .st file does the > same on 2.0 and 1.2 Yes, that's the problem. It's PasteUpMorph that handles all the dropped files. I want to make a custom Morph, DropZone, that handles dropped files. Of course i could alter PasteUpMorph, but there is a functionality that worked in 1.2 and works in Squeak, that ceased to work in 1.3+, that allowed to make morphs that handle dropped files. Background: I made an application for the psychology department of a university that parses Tobii eyetracker files (with PetitParser, which works AMAZINGLY WELL!) and does all sorts of calculations with them. I want to provide a nice interface, that allows users to drop the eyetracker files on a Pharo window to start the file processing. -- View this message in context: http://forum.world.st/Problems-with-a-Morph-that-accepts-File-Dropping-in-P… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 23, 2012

Re: [Pharo-users] Problems with a Morph that accepts File Dropping in Pharo 1.3+

by StÃ©phane Ducasse

which kind of files are you dropping because dropping a .st file does the same on 2.0 and 1.2 stef On Sep 22, 2012, at 7:01 PM, Helene Bilbo wrote: > StÃ©phane Ducasse wrote >> helene can you send the cs file? > > I send it as attachment. > > Just open an instance of DropZone in the world and start dropping files onto > it. > > In 1.2 and in Squeak it works well, in 1.3 and 1.4 it sometimes works, when > you make the morph really big, but it doesn't work or seldom works with > smaller Morphs. I could not find where the problem lies. > > helene. > DragAndDrop.st <http://forum.world.st/file/n4648486/DragAndDrop.st> > > > > -- > View this message in context: http://forum.world.st/Problems-with-a-Morph-that-accepts-File-Dropping-in-P… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Sept. 23, 2012

KaiProfiler + Pharo 1.4 cpu usage/Transcript

by Paul DeBruicker

Hi - If the transcript is open and I hover over the KaiProfiler window the Transcript is filled with mouseover information and my CPU goes to ~85%. If the transcript is closed and I hover over a my CPU runs a 2-3x what an idle Pharo-1.4 shows on my system. The transcript is filled with stuff like this: mouseOver: [(2809.0@410) mouseOver nil nil] -- nil -- nil mouseOver: [(2809.0@410) mouseOver nil nil] -- nil -- nil mouseOver: [(2809.0@410) mouseOver nil nil] -- nil -- nil mouseOver: [(2809.0@410) mouseOver nil nil] -- nil -- nil mouseOver: [(2809.0@410) mouseOver nil nil] -- nil -- nil mouseOver: [(2809.0@410) mouseOver nil nil] -- nil -- nil mouseOver: [(2809.0@410) mouseOver nil nil] -- nil -- nil mouseOver: [(2809.0@407) mouseOver nil nil] -- nil -- nil mouseOver: [(2804.0@402) mouseOver nil nil] -- nil -- nil mouseOver: [(2791.0@393) mouseOver nil nil] -- nil -- nil Is there a way to shut that off so I can have the Transcript open while viewing a profiler run? I loaded Spy by following the instructions on the Moose website. Thanks Paul

Sept. 23, 2012