[Bill Finzer]

Thanks for this. The problem is to determine whether to stack the points in each cell vertically or horizontally. Perhaps we could make that decision heuristically based on cell dimensions. Or we could add (yet another) control in the ruler menu.

Stack Points

• Vertically
• Horizontally

Got a preference?

Thanks again,

Bill

Attachments:

1. 

   image.png
   

[Bill Finzer]

Hi Traci,

Thanks for this. I wonder if you could try again to upload the screen capture, or, if that doesn’t work, send it to me by email. There are a lot of alignment issues with dot charts and I want to be sure I understand what you’re referring to.

Alternatively, tell me how to reproduce the problem with a particular dataset.

Thanks,

Bill

[Bill Finzer]

Hello,

This is a real problem since you can’t “hover” with your finger. We sort of solved this with getting attribute descriptions so that if you hold your finger down on the table’s column header, the description pops up. We could do something similar with the mean and median lines in a graph. I bet you would be happy if we did this.

Or, we could always display the mean and median values when the user is on a touch-based system. Again, I think this would help you. I’ll add both of these as “stories” in our tracking system.

In the meantime, here are two rather clumsy workarounds.

1. In addition to the mean or median, add a “movable value” to the plot. Then you can drag this value to be on top of the mean or median.
2. Define an attribute like meanHeight with the formula
   mean(height). It helps a little bit to then drag this new attribute all the way to the left of the case table to create a “parent” collection in which you just see the single value.

I hope this helps,

Bill

[Bill Finzer]

Hi Emerlyn,

Other users have reported this difficulty as well. There is discussion about it in this thread. Here is the take-home from that:

• From within CODAP choose Open from the “three strips” menu in the upper left corner.
• Choose Google Drive.
• Login to your Google account.

This is a one-time thing. After having logged via CODAP you will be able to open CODAP documents from Google Drive by double-clicking.

I hope this helps!

Bill

[Bill Finzer]

Hi Andee,

I’m sorry that you still have occasional problems with saving to and opening from Google Drive. If you get a better sense of when the problem occurs, please let us know and we’ll try to reproduce and fix it.

And thanks for the typo tip!

Bill

[Bill Finzer]

Hi Margaret,

Ah yes, parentheses! When importing, if CODAP encounters parentheses in an attribute name, it (usually helpfully but not always) treats what is inside as the unit for the attribute.

But I’m logging a bug, ’cause CODAP should be able to handle correctly the file with the entire attribute name in parens. Thanks for sending the file!

And I’m glad you figured things out,

Bill

[Bill Finzer]

Hi Margaret,

That is confusing! Nothing has changed on our end, and I just verified that importing a csv still works as usual for me.

Could you include the file itself so we can see if we get the same results and, if so, figure out why?

Thanks,

Bill

[Bill Finzer]

Hi folks,

Just to be clear, the bottom line is that you need to:

• From within CODAP choose Open from the “three strips” menu in the upper left corner.
• Choose Google Drive.
• Login to your Google account.

This is a one-time thing. After having logged via CODAP you will be able to open CODAP documents from Google Drive by double-clicking.

Note, this has nothing to do with shared CODAP documents since those are stored separately from Google Drive.

Hope this helps,

Bill

[Bill Finzer]

Hi again,

We think that once you have logged into Google Drive in CODAP things will go back to the way they have always been. It’s the transition to a new Google Drive API that has caused this.

Note: You can log in to Google Drive in CODAP by choosing OPEN and then clicking on the Google Drive option. If you’re not already logged in, that’s where you’ll see the login button.

Hope this helps and let us know of any further problems,

Bill

[Bill Finzer]

Hi Andee,

There has been a change to CODAP’s relationship to Google Drive as of yesterday. Thanks for the alert that things have changed in normal usage. We’re investigating how.

[Bill Finzer]

Hi Andee,

Try closing and remaking the map after having deleted the State attribute (or having moved County to be the first attribute). I think the map is not paying the attention it should to changes in the dataset like deleting or moving attributes.

Bill

[Bill Finzer]

Hi Andee,

Thanks for this bug report!

We’ll fix this soon,

Bill

[Bill Finzer]

Hi Andee,

Build 0567 is in QA at the moment. If it passes, the release will be later today. I’ve got my fingers crossed!

Bill

[Bill Finzer]

Hello Gerrit,

Good question! Currently links to shared documents do not expire. We plan that in the future, if a shared link has not been accessed, that is, no one has used the shared link to open the document it points to, within a certain time period, it will expire. We haven’t yet determined what the time period within which the link must be accessed will be, but we know that teachers frequently create materials that are only used every other year, so it will be at least two years.

I hope this answers your question.

Bill

[Bill Finzer]

Hi Andee,

I don’t know enough about the subtleties of working with Google Drive to understand what is going on here. I hope you were able to preserve your re-worked document.

Thanks very much for letting us know that this kind of thing can happen.

Bill

[Author]

Posts