Hi,
While browsing project loading code, I came across the following check: existingView == #none ifFalse: [ .... in ProjectLoading class >loadImageSegment ....
existingView is never bound to #none but I have seen it set to nil.
Is this a bug? .. Subbu
At Sun, 15 Mar 2009 22:52:03 +0530, K. K. Subramaniam wrote:
Hi,
While browsing project loading code, I came across the following check: existingView == #none ifFalse: [ .... in ProjectLoading class >loadImageSegment ....
existingView is never bound to #none but I have seen it set to nil.
It is bound to #none when called from QuickGuideHolderMorph>>loadPR:dir: but I think it is a bug.
-- Yoshiki
On Wednesday 18 Mar 2009 11:12:08 pm Yoshiki Ohshima wrote:
At Sun, 15 Mar 2009 22:52:03 +0530,
K. K. Subramaniam wrote:
Hi,
While browsing project loading code, I came across the following check: existingView == #none ifFalse: [ .... in ProjectLoading class >loadImageSegment ....
existingView is never bound to #none but I have seen it set to nil.
It is bound to #none when called from QuickGuideHolderMorph>>loadPR:dir: but I think it is a bug.
I missed that one. What is the difference between #none and nil?
If this is a bug, should the bug be filed in laptop.org or the tracker in squeakland.org?
Subbu
At Mon, 23 Mar 2009 18:38:04 +0530, K. K. Subramaniam wrote:
On Wednesday 18 Mar 2009 11:12:08 pm Yoshiki Ohshima wrote:
At Sun, 15 Mar 2009 22:52:03 +0530,
K. K. Subramaniam wrote:
Hi,
While browsing project loading code, I came across the following check: existingView == #none ifFalse: [ .... in ProjectLoading class >loadImageSegment ....
existingView is never bound to #none but I have seen it set to nil.
It is bound to #none when called from QuickGuideHolderMorph>>loadPR:dir: but I think it is a bug.
I missed that one. What is the difference between #none and nil?
I don't really know but it appears that these should mean the same thing.
If this is a bug, should the bug be filed in laptop.org or the tracker in squeakland.org?
This appears that non-OLPC specific, and non-sugar specific. So, squeakland.org would be the place from now on.
To settle these things down, there would be a stage where there are some confusion on where to file bugs. My suggestion here is to go ahead and try with your commonsense and soon enough examples will be set and it is less confusing.
-- Yoshiki
etoys-dev@lists.squeakfoundation.org