Print button not responding in OI10.1 OIPI classic (OIPI)
At 17 JAN 2022 07:11:16PM cmeyer wrote:
OI10.1
Changed the SYSENV CFG.OIPI to Setprinter1 to invoke the old OIPI but now the print button in the bottom left hand corner does not respond. The printer setup button is OK (next button to the right).
I need to have the classic OIPI option as most of the forms are not compatible with OIPI.NET.
Not sure if this is a bug or I need to change any other parameters to have Setprinter1 working.
Also, using OIPI.NET the resulting screen report is behind the main MDI therefore have to minimise the MDI to view the sreen report.
Any advice would be grateful.
Chris
At 17 JAN 2022 07:14PM cmeyer wrote:
Sorry I should have said VSPRINTER1 not SETPRINTER1 in the above.
Chris
At 19 JAN 2022 12:26AM Barry Stevens wrote:
Sorry I should have said VSPRINTER1 not SETPRINTER1 in the above.
Chris
I can confirm that I can also see this BUG!!!
At 19 JAN 2022 01:03AM cmeyer wrote:
Also, the OIPI classic export function still displays left over email controls that are no longer required. A cleanup is in order.
Chris
At 19 JAN 2022 07:30PM bshumsky wrote:
Also, the OIPI classic export function still displays left over email controls that are no longer required. A cleanup is in order.
Chris
Hi, guys. I can confirm that this is indeed a bug, and we'll see if it's possible to put together a patch that can resolve the issue.
Chris, what "email controls" are you specifically referencing in the OIPI "Classic" dialog?
Thanks,
- Bryan Shumsky
At 20 JAN 2022 03:30AM cmeyer wrote:
Sorry, not the email but a missing file name edit line on the OIPI classic Export function. I am not sure if the … control functions correctly.
Chris
At 20 JAN 2022 04:09AM cmeyer wrote:
My mistake. the behaviour in OI10.1 is different to OI9.4.6. The filename edit line is not visible on radio button "None" where as in OI9.4.6 it is visible. When I selected PDF the edit line became visible.
Sorry for misleading you all.
Chris.
At 24 JAN 2022 03:14PM bshumsky wrote:
There is a new patch available to download that fixes the OpenInsight 10.1 OIPI "Classic" Print Button Not Responding issue described here. Please go to the Works Downloads section of the website and follow the instructions to download and install the patch.
Please let me know if you have any problems, or if this does not resolve the problem for you.
Thanks,
- Bryan Shumsky
At 24 JAN 2022 03:34PM Donald Bakke wrote:
There is a new patch available to download that fixes the OpenInsight 10.1 OIPI "Classic" Print Button Not Responding issue described here. Please go to the Works Downloads section of the website and follow the instructions to download and install the patch.
Please let me know if you have any problems, or if this does not resolve the problem for you.
Thanks,
- Bryan Shumsky
Bryan - Thanks for the patch. Is is possible to default the second prompt for a path to the one we just entered in the first prompt? That would make it very convenient for most scenarios.
At 24 JAN 2022 03:41PM bshumsky wrote:
Bryan - Thanks for the patch. Is is possible to default the second prompt for a path to the one we just entered in the first prompt? That would make it very convenient for most scenarios.
Hi, Don. I agree; unfortunately, the "make an RDK into an EXE" tool doesn't seem to have that currently as an option. Perhaps that can be an enhancement for the next release.
Alternatively, we could just provide the RDK files as a zip instead of, or in addition to, the self-installing exe, if there is a demand for that…?
- Bryan Shumsky
At 25 JAN 2022 12:42AM Donald Bakke wrote:
Bryan - Thanks for the patch. Is is possible to default the second prompt for a path to the one we just entered in the first prompt? That would make it very convenient for most scenarios.
Hi, Don. I agree; unfortunately, the "make an RDK into an EXE" tool doesn't seem to have that currently as an option. Perhaps that can be an enhancement for the next release.
Alternatively, we could just provide the RDK files as a zip instead of, or in addition to, the self-installing exe, if there is a demand for that…?
- Bryan Shumsky
The cool takeaway from this is that you are using a tool written within OI to build your own RDK installer.
As far as demand for a separate RDK, I would fall into that camp. Options are generally favorable.
At 25 JAN 2022 08:01AM bshumsky wrote:
The cool takeaway from this is that you are using a tool written within OI to build your own RDK installer.
As far as demand for a separate RDK, I would fall into that camp. Options are generally favorable.
Hi, Don. Indeed, in the RDK tool, there has (for the last several releases at least) been an option to create a self-installing exe from the RDK. That's the bit that I used when I made the patch…
I'll see if I can add in the "RDK only" option as well to the patch.
- Bryan Shumsky