pyILPER 1.6.0 Beta 3 and LIFUTILS 1.7.7 Beta 1

[jsi]

I just published the third beta of the upcoming pyILPER version 1.6.0 on GitHub.

The list of enhancements and changes is quite extensive.

Beta testers are very welcome. You can install a beta version without troubling your production version. See the instructions at the bottom of this document.

The LIFUTILS got considerable internal changes, an installer for mac OS and two new utilities to handle Eramco MLDL-OS packed rom files. The integration of the LIFUTILS into pyILPER was improved.

Regards
Joachim

[rprosperi]

(11-19-2017 12:53 PM)jsi Wrote:  I just published the third beta of the upcoming pyILPER version 1.7.0 on GitHub.

The list of enhancements and changes is quite extensive.

Joachim - This is quite an amazing upgrade, it contains a huge amount of improvements, thanks so much for including features from our feedback, especially copy from the terminal, printer and scope windows. I will try to test this over Thanksgiving break as time allows.

FYI - Above says 1.7.0, I think it's just 1.6.0... unless 6 is being used for development only.

Thanks!

[jsi]

(11-19-2017 02:32 PM)rprosperi Wrote:  FYI - Above says 1.7.0, I think it's just 1.6.0... unless 6 is being used for development only.

A typing error. Just corrected.
Thanks

[Dave Frederickson]

Very nice!

Feature Requests:

* 2225B emulation with full character and graphics compatibility. Output to pdf.

* Better 7470 simulation. Some of the calculator emulators simulate the clicks and whirrs of tape drives or card readers. Back in the day I could be mesmerized by watching plotters so I'd like to see the plotter emulation draw the lines, ellipses, and characters rather than just display the final output. You know, when you're not busy.

Dave

[Dave Frederickson]

(01-01-2018 03:41 PM)Geir Isene Wrote:  Feature request: Make the writing to Printer1.log immediate after a print command is sent. Sometimes it takes minutes before the printing is written to Printer1.log.

I think if you clear the Log Printer 1 check box it will flush the write buffer and close the file without the wait. If that doesn't work, closing and reopening the program will close the log file.

[Sylvain Cote]

(01-01-2018 04:28 PM)Geir Isene Wrote:  Yeah, but why not just have the program simply write to the printer log file immediately after a print command is issued?

I have not tested it, but it should work.
Here for my file, your pyilper package and python version may have a different name, but you should get the idea.

Edit file : [home_folder]/miniconda3/pkgs/pyilper-1.6.0-py36hefe0d2b_0/lib/python3.6/site-packages/pyilper/pilwidgets.py
In class : class LogCheckboxWidget(QtWidgets.QCheckBox):
Modify method : logWrite
Before:

Code:

def logWrite(self,line):
   if self.log is None:
      return
   try:
      self.log.write(line)
   except OSError as e:
   ...

After:

Code:

def logWrite(self,line):
   if self.log is None:
      return
   try:
      self.log.write(line)
      self.log.flush()
   except OSError as e:
   ...

Sylvain

[Sylvain Cote]

(01-04-2018 10:06 AM)Geir Isene Wrote:  Didn't work.

Surprized, I will investigate tonight.

[jsi]

I will attend to that in favour of configurable log buffering behaviour. Logging is used by all virtual device types in pyILPER with the exception of the terminal. So stay tuned.

In the meantime you can always flush the buffer by turning logging off.

Regards
Joachim

[jsi]

You may try the latest commit on GitHub

[jsi]

Did you uncheck the new "Buffer log files" (Default is on) option in the pyILPER configuration menu ? User visible changes are documented in the release notes. This applies for development versions too.
You find them in the miscellaneous section of the online manual.