01-18-2025, 12:39 PM
I have not noticed a possibility to attach a file to a PN in the forum. I do not want yet to attach the XML file to a posting because the experiment is still work in progress. Later on I plan to have a dedicated thread for that experiment. For the time being I share the related XML code to illustrate the issue with the if block I mentioned before:
Final experiment export from old editor:
Then import to new editor and export from new editor without any manual changes in-between:
Notice how greater="true" turned into equal="true".
And another update on what I mentioned before: it is about accidentally pressing the back button on my mouse, which happened in the meanwhile two more times in front of my screen (I hit this button accidentally with my hand while moving the keyboard around on my desk and colliding with the mouse). Unfortunately there is no software / driver from the manufactuarer to disable these mouse buttons. But is it really necessary to use another mouse without such extra buttons? No, it is not, as I found out only today. Because it is possible to navigate again into the editor. But reloading the experiment again into the editor takes 10 long seconds which is close to forever if you are in fear that you lost your unsaved changes. When this happened to me the first time I was not patient enough to wait this time, I also did not new back then that just navigating back and waiting would solve this problem. The editor, the experiment, and the eternal Internet connection, which never is fast enough. An end user's facepalm experience. I would nevertheless vote for a safety popup when navigating away from the editor. A popup that the old editor was providing and which was indicating to me that I would lose my changes in case I was about to exit the whole browser while having 15+ tabs open.
Another delay experience when apparently communicating with the server. But I'm not sure what happened in this case, because I do not know which activities in the new editor are local activities being executed only in my browser on my device or which actually require communication with a server (maybe to generate the QR code). Anyways, a week back maybe and only one time, close to German midnight, there was a freeze situation in the editor in my browser. For about 30 to 60 seconds, I don't remember exactly, there was no reaction by the editor on my inputs, and, of course, I cannot tell what was the actual reason for this freeze, my computer?, the Internet connection?, the server? During the freeze my user input still was being recorded and apparently was applied after the freeze was over, leading to several changes to blocks, which I was not noticing, because I was not expecting such a thing and because after the freeze another section of the Analysis tab was displayed than before (there was some vertical scrolling applied, apparently). It took serval days and some experiment runs to identify these unwanted changes and to correct them again. Would be good to know at which actions in the editor some server call is involved and which other actions are being executed only locally. Is there at all a server side session while I locally edit my experiment? Are there scheduled server restarts introducing downtimes during which I should not use the editor? Can I have my experiment opened in the browser for weeks without losing any possible connection to the server? Or should I save my experiment and close the browser tab each time I turn off my computer?
Final experiment export from old editor:
Code:
<phyphox xmlns="http://phyphox.org/xml" xmlns:editor="http://phyphox.org/editor/xml" version="1.7" editor:version="1.0" locale="en">
<if editor:uuid="1544" editor:posx="1460" editor:posy="1780" less="false" equal="false" greater="true">
<input as="a" clear="false">lat_count</input>
<input as="b" type="value">2</input>
<input as="true" clear="false">lat(-2)_append</input>
<input as="false" type="empty" />
<output as="result">lat(-2)_if_3+_fixes</output>
</if>Then import to new editor and export from new editor without any manual changes in-between:
Code:
<phyphox xmlns="https://phyphox.org/xml" version="1.18">
<if equal="true">
<input as="a" keep="true">lat_count</input>
<input type="value" as="b">2</input>
<input as="true" keep="true">lat(-2)_append</input>
<input type="empty" as="false"></input>
<output>lat(-2)_if_3+_fixes</output>
</if>Notice how greater="true" turned into equal="true".
And another update on what I mentioned before: it is about accidentally pressing the back button on my mouse, which happened in the meanwhile two more times in front of my screen (I hit this button accidentally with my hand while moving the keyboard around on my desk and colliding with the mouse). Unfortunately there is no software / driver from the manufactuarer to disable these mouse buttons. But is it really necessary to use another mouse without such extra buttons? No, it is not, as I found out only today. Because it is possible to navigate again into the editor. But reloading the experiment again into the editor takes 10 long seconds which is close to forever if you are in fear that you lost your unsaved changes. When this happened to me the first time I was not patient enough to wait this time, I also did not new back then that just navigating back and waiting would solve this problem. The editor, the experiment, and the eternal Internet connection, which never is fast enough. An end user's facepalm experience. I would nevertheless vote for a safety popup when navigating away from the editor. A popup that the old editor was providing and which was indicating to me that I would lose my changes in case I was about to exit the whole browser while having 15+ tabs open.
Another delay experience when apparently communicating with the server. But I'm not sure what happened in this case, because I do not know which activities in the new editor are local activities being executed only in my browser on my device or which actually require communication with a server (maybe to generate the QR code). Anyways, a week back maybe and only one time, close to German midnight, there was a freeze situation in the editor in my browser. For about 30 to 60 seconds, I don't remember exactly, there was no reaction by the editor on my inputs, and, of course, I cannot tell what was the actual reason for this freeze, my computer?, the Internet connection?, the server? During the freeze my user input still was being recorded and apparently was applied after the freeze was over, leading to several changes to blocks, which I was not noticing, because I was not expecting such a thing and because after the freeze another section of the Analysis tab was displayed than before (there was some vertical scrolling applied, apparently). It took serval days and some experiment runs to identify these unwanted changes and to correct them again. Would be good to know at which actions in the editor some server call is involved and which other actions are being executed only locally. Is there at all a server side session while I locally edit my experiment? Are there scheduled server restarts introducing downtimes during which I should not use the editor? Can I have my experiment opened in the browser for weeks without losing any possible connection to the server? Or should I save my experiment and close the browser tab each time I turn off my computer?