# More learning in geogebra

Posted on March 30, 2018

(Category:   boring commentary on learning computer stuff.)

First, a Canvas observation:   somebody tweeted about the amazing community and linked to a discussion question.  It exemplified Canvas.  A person posted an issue – wanting to make an “image gallery” (with explanation), and was told “well, you can’t do that in Canvas.”   The person expressed her disappointment and frustration with their school’s switch to Canvas.

The discussion then went in awesome directions as creative, intelligent, constructive people talked about different ways to do what they wanted and work around problems.

Doesn’t make the actual program less disappointing or frustrating, though.  For this example, I think the cool ideas and workarounds would more than suffice, but there are (so) many other issues that people will creatively, intelligently talk about… but the *student* is the one who has to do the “workaround,” like the student earlier this week (NOT in Canvas — and that platform doesn’t have as amazing a community, and yes, I do wonder if it’s because of the stupid, cheesy, addictive “community ranking” where I’m still in the top 125 yes I checked).

Working on “connecting representations” in Geogebra with mad fantasies about it actually being useful and adaptable.   Couple things:

• include the ‘general concept’ that yes, visual thinkers made this thing. The syntax is what tells the program what kind of object you’re entering. So when you say anyName = If(boolean, “text1”, “text2”)   it will then know this is a text object showing as text1 if the boolean is true, and text2 if the boolean is false.   You don’t have to say “text anyName =” and if you do it will spew an error and ask what text means.
• I made the non-starting points of my images defined by the first point.   The second part of the number line is K + (7,0)  so it moves forward 7 on the x line and 0 on the y line.   (yes, this must have taken tons and tons and tons and tons of work. Visual thinkers astound me.)   OOPS NO!!!   Don’t do this.   It means that you can only drag the image from the first point.   GOing to try just making the points unselectable.  That works 🙂
• Same ‘visual’ concept for “conditions to be shown.”   Don’t say goToNext=false  – it replaces the equals sign with its equivalent to === … !goToNext gets transformed into the weird not symbol in front of it.
• include in the tutorial that yes, a lot of things get entered one way and display some other way or ways.  Subscripts are entered w/ underscore, show up as subscript except when they show up in brackets.  OH, and if you are putting it in the “conditions for it to show up” window, either copy and paste it or do the bracket thing b/c CheckIcon_{2a}  is what it needs.   _2a won’t do it.  (You’re just supposed to know that.)

Also remembering I need to prioritize *making* the tutorial for doing the number line, which will take almost precisely 3 times as long as the not very long it should take 🙂

Sigh, I am *hoping* that I will say “you made a fool of yourself!” but… the “conditions to show object”  doesn’t seem to follow its logic.  If I say two things have to be false for it to show, and they are, it still doesn’t show.   Straight up logic.  So, there will be some weird “oh, you were supposed to know that for *this* you need to…” that will be tucked back somewhere in the documentation.

Time to go!