Activity for Stefan Zieker
-
Stefan Zieker modified a comment on discussion Bug Reports
Hi, I reuploaded ScriptCommunicator 06.10 for Linux. Here the names of libraries are correct. Thx for reporting this.
-
Hi, I reuploaded ScriptCommunicator 06.10 for Linux. Here the names of libraries are correct.
-
Hi, you can try this: Go to your documents folder, rename or delete the 'ScriptCommunicator' folder and then start ScriptCommunicator.
-
Hi, you cannot download it directly. You have to install Qt on your PC and then copy the QtDesigner executable and the needed QT libraries.
-
Hi, I never tried it without an async reader. But yes, it seems that is it not possible without an asymc reader.
-
Hi, I tested it with Pop_OS 22 and had the the same error. I uploaded a new version for Linux (6.6.1) which now starts on Pop_OS 22. Thx for reporting this.
-
Hi, on my Ubuntu 22 everthing works fine. If you want you can download Qt6.4.3 and look for the missing librariers there. I'm busy at the moment. But I will intall your OS in a virtual machine this weekeend and try it out for mysself.
-
Which version of ScriptCommunictor do you use and on which which platform (Linux, Windows or MacOs) do you use it? I added foo() to a script and ScriptCommunictor showed an error and the script was stoped (that's how it should be).
-
Which version of ScriptCommunictor do you use and on which which platform (Linux, Windows or MacOs) do you use it? I added foo() to a script and ScriptCommunictor showed an error and the script was stoped (that's how it should be).
-
Which version of ScriptCommunictor do you use and on which which platform (Linux, Windos or MacOs) do you use it? I added foo() to a script and ScriptCommunictor showed an error and the script was stoped (that's how it should be).
-
Which version of ScriptCommunictor and on which which platform (Linux, Windos or MacOs) do you use it? I added foo() to a script and ScriptCommunictor showed an error and the script was stoped (that's how it should be).
-
It is bug. It worked when I used the old Qt script interpreter (Qt 5.14.2). I migrated to Qt 6.4.3 a few month ago. This version has a new interpeter. I will look into it when I have time. Thx for reporting this.
-
I will look into when I have time. Thx for reporting this.
-
np :-)
-
You can use the eval() function. If you have for example 2 line edits with the name UI_Line0 and UI_Line1 you can do this: for(var i = 0; i < 2; i++) { eval("UI_Line" + i).setText("text" + i); }
-
Yes, you can use the eval() function. If you have for example 2 line edits with the name UI_Line0 and UI_Line1 you can do this: for(var i = 0; i < 2; i++) { eval("UI_Line" + i).setText("text" + i); }
-
Yes, you can use the eval() function. If you have fo rexample 2 line edits with the name UI_Line0 and UI_Line1 you can do this: for(var i = 0; i < 2; i++) { eval("UI_Line" + i).setText("text" + i); }
-
It is not a cost think. I have kids and a full time job. So I have no time for it.
-
thx :-)
-
It is not the cost think. I have kids and a full time job. So I have no time for it.
-
I think String.prototye.format and String.prototype.keys are not standard JavaScript. Look here : https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String
-
I think String.prototye.format and String.prototype.keys are not standart JavaScript. Look here : https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String
-
Yes, the user has to take care of it. What I usually do is this: var g_storedReceivedData = Array(); function dataReceivedSlot(data) { //Save the received data. g_storedReceivedData = g_storedReceivedData.concat(data); //Do something with data }
-
Yes, the user has to take care of it. What I usually do is this: function dataReceivedSlot(data) { //Save the received data. g_storedReceivedData = g_storedReceivedData.concat(data); //Do something with data }
-
It is not the cost think. I have kids and a full time jop. So I have no time for it.
-
The JavaScript functions supported by ScriptCommunicator can be found here: https://wiki.qt.io/JavaScript The ScriptEditor is just a simple editor deleloped by me. The intention was to have an editor for simple script (like these in the example folder). I had/have no time to implement an editor that fully supports the modern JavaScript. ScriptCommunicator and the ScriptEditor are open source. So you can do it yourself if you like.
-
ScriptCommunicator uses the the Qt class QJSEngine to execute the scripts. If this class does not support these functions, I can't do anything about it.
-
Hi, JavaScript is based on ECMA. But it extends it. And on top, some browsers add there own JavaScript functions that other browsers don't have. Therefore you cannot execute all JavaScript code with ScriptCommunicator. Can you upload the code that does not work ?
-
Hi, JavaScript is based on ECMA. But it extends it (some browser for example have JavaScript functions that others don't have). Therefore you cannot execute all JavaScript code with ScriptCommunicator. Can you upload the code that does not work ?
-
Hi, JavaScript is based on ECMA. But it extends it (some browser for example have JavaScript functions that others don't have). Therefore you cannot execute all JavaScript code with ScriptCommunicator.
-
Hi, JavaScript is based on ECMA. But it extends it. Therefore you cannot execute all JavaScript code with ScriptCommunicator.
-
Hi, you should use the signal/slot mechanism. function dataReceivedSlot(data) { //Do something with the received data. } scriptInf.dataReceivedSignal.connect(dataReceivedSlot); scriptInf.sendString("TestData");
-
Hi, no, but you can call setWindowPositionAndSize to set the position (and size) of your window.
-
Hi, I migrated ScriptCommunicator from 5.14.2 to Qt 6.4.2. In this Qt version there is no script debugger, therefore I had to remove this functionality.
-
I will add this to the manual for the next release. Thx for reporting this.
-
Hi, you have to call scriptInf.dataReceivedSignal.disconnect(rxCallback) or call connect only once. If you don't do this the signal is connected several times to the slot function and therefore the slot function will be called several times.
-
Hi, you are right. It is version 06.06. I only forgot to increase the version number. I fixed it and uploaded a new release for windows. Thx for reporting this.
-
Hi, ScriptCommunicator has only a serial port (the FTDI driver creates a virtual serial port) and no specific FTDI interface. To implement this I would have to add a complete new interface type. Sorry your use case is to specific to add an extra interface to ScriptCommunicator. But you can do it yourself in your script. You can write a wrapper DLL for the FTDI interface DLL and call the corresponding functions. For an example see exampleScripts\WorkerScripts\LoadLibrary and chapter Dynamic link libraries...
-
Hi Adam, I have already created a new release of ScriptCommunicator (6.06). This version uses Qt6.4.3 instead of Qt6.4.2. Regards Stefan
-
Hi Adam, can you test the attached version of ScriptCommunicator? I switched from Qt 6.4.2 to QT 6.4.3 and the test script does not crash anymore (maybe it is this bug: QTBUG-108450 REG: Qt 6.3.2 WinOverlappedNotifier possible crash). PS: You should not call bringWindowsToFrontSlot (line 1408). This is an internal function (even it can be called from script). Where did you find that function in the documentation? The reason is that functions of GUI elements must only be called in the main thread....
-
Hi Adam, I executed your script and connected it via a virtual serial port to a second instance of ScriptCommunicator (to see what is sent). I can see that your script sends AT+CIO?*aa0f\r every second. But ScriptCommunicator does not crash. Must I sent something to the script to provoke a crash? Regards, Stefan
-
Hi Adam, thx for your script. I will test it on thursday (I'm on vacation at the moment(Berlin)). Regards, Stefan
-
Can you run your script with the test version of ScriptCommunicator in the attachment please?
-
Can you run your script with the test version of ScriptCommunicator in the attachement please?
-
Hi Adam, I did run a serial port test script and everything worked fine. ScriptCommunicator just routes the QSerialPort functions. I think it must be a combination of your calls that crashes in the new version (Qt 6.4 instead of Qt 5.14). Can you send me your scipt so that I can maybe reproduce it? Regards, Stefan
-
Hi Adam, I did run a serial port test script and everything works fine. ScriptCommunicator just routes the QSerialPort functions. I think it must be a combination of your calls that crashes in the new version (Qt 6.4 instead of Qt 5.14). Can you send me your scipt so that I can maybe reproduce it? Regards, Stefan
-
Hi Adam, I did run a serial port test script and everything works fine. ScriptCommunicator just routes the QSerialPort functions. I think it must be a combination of your calls that crashes in the new version (Qt 6.4 insteasd of Qt 5.14). Can you send me your scipt so that I can maybe reproduce it? Regards, Stefan
-
Hi Adam, I did run a serial port test script and everything works fine. ScriptCommunicator just routes the QSerialPort functions. I think it must be a combination of your calls that crashed in the new version (Qt 6.4 insteasd of Qt 5.14). Can you send me your scipt so that I can maybe reproduce it? Regards, Stefan
-
:-)
-
Hi, I changed ScriptCommunicator so that if it detects a not supported Widget (e.g. LCD number) it adds a message in the script window instead of showing a message box. Now your scirpt can be started automatically. I added a prerelease of ScriptCommunicator in the attachment.
-
:-)
-
Hi Mark, I will put it on my list.
-
Hi Mark, I want to test something. Can you run your script with the attached ScriptComunicator (I changed sleepFromScript)? Note: It runs only with the 6.4 Libraries.
-
Hi Mark, I want to test something. Can you run your script with the attached ScriptComunicator (I changed sleepFromScript)?
1 >