Forum Replies Created
-
Posts
-
You’re right. If you want a second document, then choose New. This will open a new CODAP tab. (But I believe it will not know about your last location on Google drive. Sorry.)
Hi Andee,
You should be able to Undo most everything. Getting an Error is evidence of a bug.
Fortunately, I just checked, and this particular bug is fixed in the next release of CODAP.
Thanks for the bug report! We really appreciate it.
Bill
Hi Christine,
At the moment CODAP will only plot points from one dataset, and you don’t have the ability to choose which one. So, the only workaround I can suggest is that you make documents with just one of the datasets at a time.
We are working right now on giving you full control over as many point or polygon map layers as you like from as many different datasets as you like. This should release around the end of August.
Bill
I find that if I don’t close the document but go straight to Open, I get taken to the same place.
Clearly this area needs work!
Hi Andee,
Good catch with the ambiguous instructions.
It should say something like “Click in an empty cell in the bottom row.”
Bill
Hi Andee,
Good suggestion. CODAP does take you back to the last location from which you opened, provided you do the Open from the same browser tab. But, if you open CODAP in a new tab, it doesn’t remember where you were opening from in the other tab. But, I suppose it could, using cookies or something like that.
Bill
Hi Andee,
Here’s one example:
if(Age<20,”Young”,”Not Young”)
Basically anywhere you might return a number, you can return a quoted string.
Bill
Hi Andee,
You may already know that you can change the way an attribute is treated on a given graph by clicking on the attribute name on the axis and choosing Treat as Numeric or Categorical if that’s the direction you’re going.
Alternatively, you can bring up the Attribute Properties dialog box and change the type of the attribute to numeric. This will have the effect that the non-numeric values will be ignored in any graphs you make and the attribute will be treated as numeric.
Bill
Hi Andee,
It’s possible the SmartBoard is translating your gestures into touch events. If this is the case, there are many known CODAP bugs with touch devices. I believe the two you mention are among them.
The good news is that we’re about to come out with a release (~mid-August) that should fix most of the touch device problems.
Bill
Hi Sue,
As Dan points out, the fact that CODAP becomes fully resident on each user’s computer should rule out any problems with large numbers of users.
As to stability over time, CODAP is evolving so there will continue to be improvements in performance and usability as well as enhanced features. It’s certainly possible that some changes in CODAP will require changes to the instructions in the course materials. One way to deal with this is for your institution to serve a single, stable version of CODAP during a run of the course. This is very straightforward, amounting to little more than unzipping a file onto your server and pointing your users to that URL.
Hope this helps,
Bill
Hi Kristyn,
I can think of one way, but not sure if it will do what you want.
- Suppose you have an attribute A and you have typed values into the first four cases.
- Create an attribute B with the formula: if(caseIndex<5,A,random()). This copies the entered values from A into B and puts random numbers in the new cases as values for B.
- Now add a bunch more cases; e.g. by clicking on row 5’s index and choosing Insert Cases.
Bill
Hi Andee,
I’ve seen this too, and you’re absolutely right. It seems to be a relatively newly introduced bug that needs fixing.
Bill
Hi Kristyn,
Yes, you can restrict the range. Here is an example that plots the square root of between 3 and 9:
if(x>3&x<9, sqrt(x),””)
Re: 2 functions—A possible trick (not recommended) is to make a second graph with the second function. Then give it a transparent background and place it on top of the first graph.
But eventually we’ll provide the ability to plot multiple functions in a graph with no tricks.
Bill
I was able to replicate the problem.
- Create a new document and change its name to “First.”
- Save this document to Google Drive.
- In CODAP, change the document name to “Second.”
- In the Share menu choose Get Link to Shared View.
Notice that the name of the document reverts to First immediately. (Bug!)
If you go on to get the link and open it, the shared view has the name First. In fact, all trace of “Second” is gone.
Andee, I’d say you’ve uncovered a nice little rat’s nest of bugs here! Thanks.