mondrian bug?
Locked
 
|
view shape rectangle size: 20. view interaction action: #inspect. view interaction whenEnteringUpdateNode: [:node | view interaction forwarder. view nodes: (Set allSubclasses). view interaction forwarder. view edgesFrom: #superclass. view treeLayout ] whenLeavingUpdateNode: [:node | ] withLayoutUpdate: true. view nodes: (1 to: 3) when I try this example I do not see the tree representing subclasses. Stef _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
apparently the problem is due to the fact that there is a second dot in the script
On May 25, 2011, at 3:25 PM, Stéphane Ducasse wrote: > > > view shape rectangle size: 20. > view interaction action: #inspect. > view interaction > whenEnteringUpdateNode: [:node | view interaction forwarder. > view nodes: (Set allSubclasses). > view interaction forwarder. > view edgesFrom: #superclass. . ^^^^ > view treeLayout ] > whenLeavingUpdateNode: [:node | ] withLayoutUpdate: true. > view nodes: (1 to: 3) > I removed it when I copied and pasted the mail. > when I try this example I do not see the tree representing subclasses. > > Stef > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
The issue is that Set allSubclasses does not return a tree. Use Set withAllSubclasses, and you will get a tree.
Doru On 25 May 2011, at 15:28, Stéphane Ducasse wrote: > apparently the problem is due to the fact that there is a second dot in the script > > On May 25, 2011, at 3:25 PM, Stéphane Ducasse wrote: > >> >> >> view shape rectangle size: 20. >> view interaction action: #inspect. >> view interaction >> whenEnteringUpdateNode: [:node | view interaction forwarder. >> view nodes: (Set allSubclasses). >> view interaction forwarder. >> view edgesFrom: #superclass. . > ^^^^ >> view treeLayout ] >> whenLeavingUpdateNode: [:node | ] withLayoutUpdate: true. >> view nodes: (1 to: 3) >> > > I removed it when I copied and pasted the mail. > >> when I try this example I do not see the tree representing subclasses. >> >> Stef >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "What we can governs what we wish." _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
the original problem was that I did not get anything.
Because the error apparently was trapped. On May 25, 2011, at 3:34 PM, Tudor Girba wrote: > The issue is that Set allSubclasses does not return a tree. Use Set withAllSubclasses, and you will get a tree. > > Doru > > > On 25 May 2011, at 15:28, Stéphane Ducasse wrote: > >> apparently the problem is due to the fact that there is a second dot in the script >> >> On May 25, 2011, at 3:25 PM, Stéphane Ducasse wrote: >> >>> >>> >>> view shape rectangle size: 20. >>> view interaction action: #inspect. >>> view interaction >>> whenEnteringUpdateNode: [:node | view interaction forwarder. >>> view nodes: (Set allSubclasses). >>> view interaction forwarder. >>> view edgesFrom: #superclass. . >> ^^^^ >>> view treeLayout ] >>> whenLeavingUpdateNode: [:node | ] withLayoutUpdate: true. >>> view nodes: (1 to: 3) >>> >> >> I removed it when I copied and pasted the mail. >> >>> when I try this example I do not see the tree representing subclasses. >>> >>> Stef >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > www.tudorgirba.com > > "What we can governs what we wish." > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
> the original problem was that I did not get anything.
> Because the error apparently was trapped. Yes. Errors are trapped during an interaction. This is the only relatively reliable solution I have found to not get a recursive debugger opening loop. Alexandre > > On May 25, 2011, at 3:34 PM, Tudor Girba wrote: > >> The issue is that Set allSubclasses does not return a tree. Use Set withAllSubclasses, and you will get a tree. >> >> Doru >> >> >> On 25 May 2011, at 15:28, Stéphane Ducasse wrote: >> >>> apparently the problem is due to the fact that there is a second dot in the script >>> >>> On May 25, 2011, at 3:25 PM, Stéphane Ducasse wrote: >>> >>>> >>>> >>>> view shape rectangle size: 20. >>>> view interaction action: #inspect. >>>> view interaction >>>> whenEnteringUpdateNode: [:node | view interaction forwarder. >>>> view nodes: (Set allSubclasses). >>>> view interaction forwarder. >>>> view edgesFrom: #superclass. . >>> ^^^^ >>>> view treeLayout ] >>>> whenLeavingUpdateNode: [:node | ] withLayoutUpdate: true. >>>> view nodes: (1 to: 3) >>>> >>> >>> I removed it when I copied and pasted the mail. >>> >>>> when I try this example I do not see the tree representing subclasses. >>>> >>>> Stef >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> [hidden email] >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> -- >> www.tudorgirba.com >> >> "What we can governs what we wish." >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
so at least fix the script :)
Stef On May 25, 2011, at 6:25 PM, Alexandre Bergel wrote: >> the original problem was that I did not get anything. >> Because the error apparently was trapped. > > Yes. Errors are trapped during an interaction. > This is the only relatively reliable solution I have found to not get a recursive debugger opening loop. > > Alexandre > >> >> On May 25, 2011, at 3:34 PM, Tudor Girba wrote: >> >>> The issue is that Set allSubclasses does not return a tree. Use Set withAllSubclasses, and you will get a tree. >>> >>> Doru >>> >>> >>> On 25 May 2011, at 15:28, Stéphane Ducasse wrote: >>> >>>> apparently the problem is due to the fact that there is a second dot in the script >>>> >>>> On May 25, 2011, at 3:25 PM, Stéphane Ducasse wrote: >>>> >>>>> >>>>> >>>>> view shape rectangle size: 20. >>>>> view interaction action: #inspect. >>>>> view interaction >>>>> whenEnteringUpdateNode: [:node | view interaction forwarder. >>>>> view nodes: (Set allSubclasses). >>>>> view interaction forwarder. >>>>> view edgesFrom: #superclass. . >>>> ^^^^ >>>>> view treeLayout ] >>>>> whenLeavingUpdateNode: [:node | ] withLayoutUpdate: true. >>>>> view nodes: (1 to: 3) >>>>> >>>> >>>> I removed it when I copied and pasted the mail. >>>> >>>>> when I try this example I do not see the tree representing subclasses. >>>>> >>>>> Stef >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> [hidden email] >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> [hidden email] >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> -- >>> www.tudorgirba.com >>> >>> "What we can governs what we wish." >>> >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
In reply to this post by abergel
On 25 May 2011, at 12:25, Alexandre Bergel wrote: >> the original problem was that I did not get anything. >> Because the error apparently was trapped. > > Yes. Errors are trapped during an interaction. > This is the only relatively reliable solution I have found to not get a recursive debugger opening loop. I understand the problem, have been bitten by it sufficiently when working on AM. But is there a way to display some side-effect so that the developer knows that 'something' has gone wrong? A non-modal dialog box giving some info? -- Johan Fabry [hidden email] - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
> I understand the problem, have been bitten by it sufficiently when working on AM. But is there a way to display some side-effect so that the developer knows that 'something' has gone wrong? A non-modal dialog box giving some info?
Yes. The way to do better is to render in a bitmap, then to display the bitmap. This is what I do with the non popup nodes with the bitmap cache. This is more a matter of available resource than technical challenge to make this happens. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
On May 25, 2011, at 8:00 PM, Alexandre Bergel wrote: >> I understand the problem, have been bitten by it sufficiently when working on AM. But is there a way to display some side-effect so that the developer knows that 'something' has gone wrong? A non-modal dialog box giving some info? > > Yes. The way to do better is to render in a bitmap, then to display the bitmap. ??? why? I do not understand what bitmap has to do with reporting error. I think that using what a workspace provides should be enough to catch error and show it. > This is what I do with the non popup nodes with the bitmap cache. This is more a matter of available resource than technical challenge to make this happens. > > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
>> Yes. The way to do better is to render in a bitmap, then to display the bitmap. ???
> > why? I do not understand what bitmap has to do with reporting error. Rendering the popupView in a form without displaying anything may safely raises an error, and open a debugger. If a debugger is open by a morph being displayed, then it is painted in red with a cross. But times to times, it opens many debuggers, which screws your image: it tries to call a drawOn: at each research, which opens a debugger. I spent on time on this, but this is a hard-to-track problem. It has been in squeak since I do smalltalk. Alexandre > > >> This is what I do with the non popup nodes with the bitmap cache. This is more a matter of available resource than technical challenge to make this happens. >> >> Alexandre >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
have a look at on:fork: recent cool addition introduced by igor.
It can save your day. Stef On May 25, 2011, at 9:41 PM, Alexandre Bergel wrote: >>> Yes. The way to do better is to render in a bitmap, then to display the bitmap. ??? >> >> why? I do not understand what bitmap has to do with reporting error. > > Rendering the popupView in a form without displaying anything may safely raises an error, and open a debugger. > If a debugger is open by a morph being displayed, then it is painted in red with a cross. But times to times, it opens many debuggers, which screws your image: it tries to call a drawOn: at each research, which opens a debugger. I spent on time on this, but this is a hard-to-track problem. It has been in squeak since I do smalltalk. > > Alexandre > >> >> >>> This is what I do with the non popup nodes with the bitmap cache. This is more a matter of available resource than technical challenge to make this happens. >>> >>> Alexandre >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
he he. It can do the trick
Alexandre On 25 May 2011, at 15:54, Stéphane Ducasse wrote: > have a look at on:fork: recent cool addition introduced by igor. > It can save your day. > > Stef > > On May 25, 2011, at 9:41 PM, Alexandre Bergel wrote: > >>>> Yes. The way to do better is to render in a bitmap, then to display the bitmap. ??? >>> >>> why? I do not understand what bitmap has to do with reporting error. >> >> Rendering the popupView in a form without displaying anything may safely raises an error, and open a debugger. >> If a debugger is open by a morph being displayed, then it is painted in red with a cross. But times to times, it opens many debuggers, which screws your image: it tries to call a drawOn: at each research, which opens a debugger. I spent on time on this, but this is a hard-to-track problem. It has been in squeak since I do smalltalk. >> >> Alexandre >> >>> >>> >>>> This is what I do with the non popup nodes with the bitmap cache. This is more a matter of available resource than technical challenge to make this happens. >>>> >>>> Alexandre >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> [hidden email] >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
On May 25, 2011, at 9:58 PM, Alexandre Bergel wrote: > he he. It can do the trick this is really cool :) and it can be used to secure a lot of infrastructure: announcement (done), finalization (done), fucking ui thread (on the pipe) Stef > > Alexandre > > > On 25 May 2011, at 15:54, Stéphane Ducasse wrote: > >> have a look at on:fork: recent cool addition introduced by igor. >> It can save your day. >> >> Stef >> >> On May 25, 2011, at 9:41 PM, Alexandre Bergel wrote: >> >>>>> Yes. The way to do better is to render in a bitmap, then to display the bitmap. ??? >>>> >>>> why? I do not understand what bitmap has to do with reporting error. >>> >>> Rendering the popupView in a form without displaying anything may safely raises an error, and open a debugger. >>> If a debugger is open by a morph being displayed, then it is painted in red with a cross. But times to times, it opens many debuggers, which screws your image: it tries to call a drawOn: at each research, which opens a debugger. I spent on time on this, but this is a hard-to-track problem. It has been in squeak since I do smalltalk. >>> >>> Alexandre >>> >>>> >>>> >>>>> This is what I do with the non popup nodes with the bitmap cache. This is more a matter of available resource than technical challenge to make this happens. >>>>> >>>>> Alexandre >>>>> >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> [hidden email] >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> [hidden email] >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
Sounds intriguing. I did not check, but can it be used to do parallel rendering? Perhaps this can be a solution for Glamour.
Doru On 25 May 2011, at 22:11, Stéphane Ducasse wrote: > > On May 25, 2011, at 9:58 PM, Alexandre Bergel wrote: > >> he he. It can do the trick > > this is really cool :) > and it can be used to secure a lot of infrastructure: announcement (done), finalization (done), fucking ui thread (on the pipe) > > Stef > > >> >> Alexandre >> >> >> On 25 May 2011, at 15:54, Stéphane Ducasse wrote: >> >>> have a look at on:fork: recent cool addition introduced by igor. >>> It can save your day. >>> >>> Stef >>> >>> On May 25, 2011, at 9:41 PM, Alexandre Bergel wrote: >>> >>>>>> Yes. The way to do better is to render in a bitmap, then to display the bitmap. ??? >>>>> >>>>> why? I do not understand what bitmap has to do with reporting error. >>>> >>>> Rendering the popupView in a form without displaying anything may safely raises an error, and open a debugger. >>>> If a debugger is open by a morph being displayed, then it is painted in red with a cross. But times to times, it opens many debuggers, which screws your image: it tries to call a drawOn: at each research, which opens a debugger. I spent on time on this, but this is a hard-to-track problem. It has been in squeak since I do smalltalk. >>>> >>>> Alexandre >>>> >>>>> >>>>> >>>>>> This is what I do with the non popup nodes with the bitmap cache. This is more a matter of available resource than technical challenge to make this happens. >>>>>> >>>>>> Alexandre >>>>>> >>>>>> -- >>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>>> Alexandre Bergel http://www.bergel.eu >>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Moose-dev mailing list >>>>>> [hidden email] >>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>>> >>>>> >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> [hidden email] >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> [hidden email] >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "We cannot reach the flow of things unless we let go." _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
I would not do that doru.
This is really to control error and that error does not pt the system on his knees On May 25, 2011, at 10:19 PM, Tudor Girba wrote: > Sounds intriguing. I did not check, but can it be used to do parallel rendering? Perhaps this can be a solution for Glamour. > > Doru > > > On 25 May 2011, at 22:11, Stéphane Ducasse wrote: > >> >> On May 25, 2011, at 9:58 PM, Alexandre Bergel wrote: >> >>> he he. It can do the trick >> >> this is really cool :) >> and it can be used to secure a lot of infrastructure: announcement (done), finalization (done), fucking ui thread (on the pipe) >> >> Stef >> >> >>> >>> Alexandre >>> >>> >>> On 25 May 2011, at 15:54, Stéphane Ducasse wrote: >>> >>>> have a look at on:fork: recent cool addition introduced by igor. >>>> It can save your day. >>>> >>>> Stef >>>> >>>> On May 25, 2011, at 9:41 PM, Alexandre Bergel wrote: >>>> >>>>>>> Yes. The way to do better is to render in a bitmap, then to display the bitmap. ??? >>>>>> >>>>>> why? I do not understand what bitmap has to do with reporting error. >>>>> >>>>> Rendering the popupView in a form without displaying anything may safely raises an error, and open a debugger. >>>>> If a debugger is open by a morph being displayed, then it is painted in red with a cross. But times to times, it opens many debuggers, which screws your image: it tries to call a drawOn: at each research, which opens a debugger. I spent on time on this, but this is a hard-to-track problem. It has been in squeak since I do smalltalk. >>>>> >>>>> Alexandre >>>>> >>>>>> >>>>>> >>>>>>> This is what I do with the non popup nodes with the bitmap cache. This is more a matter of available resource than technical challenge to make this happens. >>>>>>> >>>>>>> Alexandre >>>>>>> >>>>>>> -- >>>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>>>> Alexandre Bergel http://www.bergel.eu >>>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Moose-dev mailing list >>>>>>> [hidden email] >>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Moose-dev mailing list >>>>>> [hidden email] >>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>>> >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> [hidden email] >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> [hidden email] >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > www.tudorgirba.com > > "We cannot reach the flow of things unless we let go." > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
«
Return to Moose
|
1 view|%1 views
| Free forum by Nabble | Edit this page |