Cannot enter "Custom Command Line Parameter"
[Windows 10, RDM 3.5.4]
Hi,
I created a "command line" session ("Run: ping {1}") and a parameter ("Parameter #1" of type text and no default value). When opening the session, I'm not able to type anything in the designated field (no text cursor appears - see screenshot)
Custom Command Line Parameter.png
All Comments (10)
We will invesigate but if you have the time to export the session, we could start from there.
Regards
David Hervieux
Please find the file attached
Test.rdm
The test session works as expected on another computer (I copied the complete RDM application directory to the other machine). Maybe there is a dependency missing on my laptop?
I narrowed it down: the problem starts with version 3.0.3.0 - 3.0.1.0 still works...
Interestingly, if I enter a second parameter, then the first becomes visible and editable (but not the second). In this case #1 is Host and #2 is Port. In 3.0.1.0 I can see both parameters
Host-Port-Parameters.png
Last note: the second parameter seems to be there but "invisible". If I press Tab in the first field and type blindly something, the receiving command receives parameter {2}
Hello Thorsten,
Thank you for taking the time to investigate where the problem comes from.
We'll get working on this issue as soon as possible and keep you updated on the progress.
Regards,
Michaël Beaudin
Hello Thorsten,
Would you mind telling me what your DPI scaling is? I think it might be at the root of the issue.
Regards,
Michaël Beaudin
Hello,
it's at 125% ("recommended") - which Windows configured at that value automatically. No idea why.
Thorsten
Hello Thorsten,
We have managed to reproduce the issue and fixed it so that it works on our side.
The changes should be available in the next minor release of RDM.
Regards,
Michaël Beaudin
