Post Reply 
pyILPER 1.7.0 beta release
02-21-2018, 01:37 AM
Post: #14
RE: pyILPER 1.7.0 beta release
(02-19-2018 07:55 AM)jsi Wrote:  All log files are created in the pyILPER working directory which you can set in the pyILPER main configuration dialog. If not specified, pyILPER uses the Home directory which should be <root>\Users\<username> on Windows 7.

Wouldn't <root>\Users\<username>\pyilper be a better default? I think the root of the user folder is a dangerous place for folks to be handling files. One accidental deletion could cause lots of trouble.

(02-19-2018 07:55 AM)jsi Wrote:  At the moment all log file output is appended to a single file that belongs to a virtual device. A timestamp in the file identifies a particular output. Other solutions are possible - but not for 1.7.0 any more - like:
  • create a new file in the working directory every time when logging gets enabled and put the timestamp in the filename
  • ask the user to enter a new filename

I'd like to implement a solution which fits the needs of the majority of users so suggestions are welcome.

I think the most flexible and helpful solution would be as follows:
  • Maintain the current .log file scheme, appending each (Start/Stop) session with start/stop timestamps inserted, but also
  • Create a new file when logging is enabled, with 'Save As...' dialog open with default filename of PrintLog_timestamp in the current default folder
  • User can click OK to accept default or modify filename before OK
  • User can navigate to alternate folder before saving (and/or renaming) by OK
  • Canceling the dialog skips writing new session file, but global log is updated
  • File(s) closed when logging is stopped or program ends

The reason for saving both logs (the master growing file as well as the current log session file) is that often when exploring new media or working on a project, one wants to save various BASIC or TEXT files as they are explored, but also retain the full log of what was done for the full pyILPer session.

I have not encountered any problems with 1.7.0beta. I've not used the Plotter or Scope devices at all so can't comment on them, but the Terminal, Printer and Drive devices all were stable. I have not tried every possible combination of settings, but all that I did try did behave as expected, though I would describe my time as simply using rather than testing.

Also, I should note my all use was with a '71B. No time yet for trying the '75C, and no patience for 41C HP-IL.

--Bob Prosperi
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
pyILPER 1.7.0 beta release - jsi - 02-10-2018, 05:22 PM
RE: pyILPER 1.7.0 beta release - salvomic - 02-10-2018, 05:33 PM
RE: pyILPER 1.7.0 beta release - jsi - 02-11-2018, 07:32 AM
RE: pyILPER 1.7.0 beta release - jsi - 02-11-2018, 02:06 PM
RE: pyILPER 1.7.0 beta release - rprosperi - 02-11-2018, 10:47 PM
RE: pyILPER 1.7.0 beta release - rprosperi - 02-11-2018, 11:49 PM
RE: pyILPER 1.7.0 beta release - jsi - 02-12-2018, 07:23 AM
RE: pyILPER 1.7.0 beta release - rprosperi - 02-12-2018, 02:10 PM
RE: pyILPER 1.7.0 beta release - jsi - 02-12-2018, 03:24 PM
RE: pyILPER 1.7.0 beta release - rprosperi - 02-12-2018, 08:51 PM
RE: pyILPER 1.7.0 beta release - rprosperi - 02-18-2018, 05:47 PM
RE: pyILPER 1.7.0 beta release - jsi - 02-19-2018, 07:55 AM
RE: pyILPER 1.7.0 beta release - rprosperi - 02-21-2018 01:37 AM
RE: pyILPER 1.7.0 beta release - jsi - 02-21-2018, 01:27 PM



User(s) browsing this thread: 2 Guest(s)