Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Mar 28, 2017 16:44:28 GMT -5
When I use the print command, I get incorrect output. I double checked print setup, and I see ~.f for the left header and all I get is the full stop. The left footer is File Date: ~d ~t, and I get File Date: 60128-57-8 25748: . The page number, header name, and print date are correct. I made no changes to print setup.
|
|
|
Post by George on Mar 29, 2017 11:24:08 GMT -5
iprefer432: Right off, the ~.f is incorrect. I just checked my setup and I have ~f~x and it seems fine (e.g. it shows Filename.txt)
My footer is the same as yours, but I'm getting a valid 2017-03-16 13:13:00. Odd. What are your regional date/time format settings? (Shouldn't make a difference, but ....)
George
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Mar 30, 2017 8:52:47 GMT -5
George. (This problem editor is not too friendly for disabled one finger typists like me. I submitted a reply yesterday and it's not found.) The header was ~f.~x. How it got that way, I don't know. I deleted the . and no change. Blank. When I checked the date/time settings, I discovered the set zone automatically was off. I turned it on. No change. I'm running Windows 10. I keep updates current. I have a new printer. (So far no problems with it.) I believe in the Twilight Zone factor when it comes to strange problems. I've been working with computers since 1969 and seen a lot. iprefer432
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Mar 30, 2017 10:48:48 GMT -5
George. Found something else. I do the profile edit txt (or any other profile), change the automatic file save at end from off prompt to on noprompt. When I try to save the edit, I get an error "Excessive operands for NUMBER command" and have to cancel the edit. NUMBER is set to off. iprefer432
|
|
|
Post by George on Mar 30, 2017 10:57:54 GMT -5
iPrefer432: I can't seem to duplicate your SAVE problem either. Could you check your profile against what I was testing with and let me know any differences, so I can duplicate your settings. Here's mine:
PROFILE TXT LOCKED, ACTION OFF, AUTOBKUP OFF, AUTOCAPS OFF, AUTONUM OFF AUTOSAVE ON NOPROMPT, CAPS OFF, CASE T, CHANGE CS, COLLATE ANSI, COLS ON EOL CRLF, FOLD OFF, HEX OFF, HILITE FIND AUTO, LRECL 0, MARK ON, MINLEN 0 NUMBER OFF, NUMTYPE NONE, PAGE OFF, PRESERVE ON, RECFM U SCROLL CSR, SETUNDO 10, SOURCE ANSI, START FIRST, STATE ON, SUBARG XXX TABS ON, XTABS 0
George
P.S. Why not just send me the xxxx.INI file from the Profile directory. Send it to support@SPFLite.com
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Mar 31, 2017 9:43:21 GMT -5
It has been sent.
|
|
|
Post by George on Mar 31, 2017 13:54:23 GMT -5
iprefer432: Got the INI, and the NUMBER thing is an outright bug. We altered the design internals for NUMBER and NUMTYPE half-way through, and we ended up with a kind of messed up hybrid of the old and new ways. (Plain sloppiness is what it is). I'll have to get a fix release out quickly.
George
|
|
|
Post by George on Apr 1, 2017 12:32:13 GMT -5
OK, got the SPFLite.INI, thanks. Everything still looks fine. I've traced exactly where this file info comes from, and it's right out of the file directory. It's a formated verion of the LastWriteTime field. Can you go into Explorer and do a Properties on a file which shows this invalid date and see what Properties shows for the Last Modified Date? Or maybe this file is not on a local drive, but a network drive? I'm kinda at a loss here.
Also, what does the date look like in File Manager?
George
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 2, 2017 10:58:14 GMT -5
I've already modified that member. Here's applicable information for another. Modified shows Sunday February 26, 2017 1:33:55 pm, and the print gives 60124-57-7 62492: . I am not using cloud storage nor any other software.
|
|
|
Post by George on Apr 2, 2017 11:40:44 GMT -5
iprefer432: Hmmm, what I can't figure out is how it creates that format. The code does it using fixed length format strings, 4 for year, 2 for month, 2 for day etc. yet yours starts out with a 5 digit number in the year position. And the -7 for day should at least be -07. And we have a 5 digit number for the hh portion of the time. ? The help info for formatting says "If the number has more digits to the left of the decimal point than there are zeros to the left of the decimal point in the format expression, the extra digits are displayed without truncation", so I suppose if I somehow get a large number, formatting will return a longer string. So that means the DateTime field I'm working with is somehow invalid. Looking at the formatting routine, it takes the filetime from the directory and then does a ToLocalTime conversion since I believe the directory times are all UTC format. What Timezone offset are you running with? George
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 3, 2017 10:28:10 GMT -5
George. UTC-06:00 Central iprefer432.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 4, 2017 9:27:06 GMT -5
1. FM. 2. I own it, ie, I can print, edit, etc. 3. Printed data is ok. Header and trailer are giving me problems.
|
|
|
Post by George on Apr 4, 2017 11:38:17 GMT -5
iprefer432: How is the file opened? i.e. Command line operand? From FM? Drag/Drop? Primary command "EDIT filename"?
Robert: feel free to go code browsing. Here's the basic path chain from PRINT:
pCmdPRINT Primary command sLPrint Print a single line TP.MacSubst Do substitution for the ~d footer operand TIP.Date To fetch the file's date sMakePrettyTime To format the date Notes:
Each tab is controlled by an Object of type cObjTabData. (See _TabData.INC)
The global pointer TP always points to the cObjTabData of the currently running tab.
Within cObjTabData is TIP, an object of the cIO class, which contains all data related to an external file. (See _ObjIO.INC) The TIP object always contains the controlling data for the file being edited in a tab.
Within TIP is an FD area which is completed from the directory structure of the file when it is opened. (See PB Help for DIR$ - DirData - for the layout)
Within the FD is FD.LastWriteTime is the date field which is formatted.
Currently I cannot see any path through cIO where the FD area would not be completed as the file is opened. maybe your eyes are better.
George
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 4, 2017 16:14:05 GMT -5
George. Just realized I may have been using spflite wrong. I get the error when I use p in the directory listing. (I get no invalid command message.) When I use edit or view to open the member then issue the print command I get correct results. Sorry for the mass confusion. iprefer432
|
|
|
Post by George on Apr 5, 2017 10:19:56 GMT -5
Aha! I can duplicate that. Once duplicated, a fix should be easy.
And no, you haven't been using SPFLite 'wrong', this is a plain simple bug. (Simple - nah! This will actually be tricky.)
George
|
|