#4352 creation bugfix

git-svn-id: http://dev.geogebra.org/svn/trunk/geogebra@36421 23ce0884-8a58-47d3-bc5c-ddf1cd5b9f9e
UDPLogger is slow if we log, and slow if we don't log... slow if we repaint, and slow if we repaint less often... so maybe GeoGebra's updateConstruction feature cannot do 1000 Hz of frequency, and we have to find a better way to visualize 1000 Hz. It surely cannot be seen real-time, but it will be necessary to visualize as a function curve, for example, so we really need to implement 1000 Hz of frequency (i.e. accept the data), but we shouldn't put this information into the entire construction real-time, but only into one GeoElement (to remember the previous values too) or maybe the spreadsheet, in my opinion

git-svn-id: http://dev.geogebra.org/svn/trunk/geogebra@36422 23ce0884-8a58-47d3-bc5c-ddf1cd5b9f9e
Bug in the previous commit (forgotten commenting), and in its comment, I meant updateCascade, not updateConstruction

git-svn-id: http://dev.geogebra.org/svn/trunk/geogebra@36423 23ce0884-8a58-47d3-bc5c-ddf1cd5b9f9e