|
Post by Jo on Jan 13, 2014 11:48:02 GMT -5
Version 7.1.4001 Box 'Delete to Recycle Bin?' in General Options is checked, but D Linecommand in Filemanager displays a Popup-Msg with 'OK to Purge ...' and after answering Yes, the File is gone and not in the Recycle Bin.
|
|
|
Post by George on Jan 13, 2014 14:05:33 GMT -5
Hi Jo, Thanks for the report, I'll go check it out.
George
|
|
|
Post by George on Jan 14, 2014 10:57:44 GMT -5
Hi again,
Bug found and fixed. We were just getting ready to package a minor fix release, so this will be included.
But I see you have been busy and maybe found some others, so I'll check them out first and stomp them.
George
|
|
|
Post by Jo on Dec 9, 2014 9:09:49 GMT -5
Yes, this was fixed on 7.1.4016, but now ... I'm using 8.1.4311 and this bug is here again :-(
Jo
|
|
|
Post by George on Dec 9, 2014 12:08:14 GMT -5
Hi Jo, Corrected. I think the bug re-appeared during the V7 to V8 conversion where just about everything internal was upgraded, poked, prodded or otherwise fiddled with. It turned out to be a simple misplaced right parenthesis. If you'd like a corrected version please download www.SPFLite.com/Files/SPFLite814343.ex_ Just rename it to SPFLite.EXE and swap it into the normal install folder. George
|
|
|
Post by Jo on Dec 10, 2014 10:23:51 GMT -5
Hi !
Downloaded SPFLite814343 and this bug is gone. But now those comment-lines with opening & closing chars (I use /* */) display another / at the end: /* comment *// The file itself is ok, without the trailing /
Jo
|
|
|
Post by George on Dec 10, 2014 11:19:32 GMT -5
Hmmm, I did a fix 8.1.4317 for a problem in this area. Thought it was stomped. I guess I'll have to go back and re-visit it.
George
|
|
|
Post by George on Dec 10, 2014 12:06:43 GMT -5
OK, revisited the code, and found the previous fix missing. I've no idea how I could have done that, but I did. Made the two line change again, and I think we're OK again. If you want the latest fixed version, please download www.SPFLite.com/Files/SPFLite814344.EX_ Rename it to SPFLite.EXE and swap it into the normal Install folder. George
|
|
|
Post by Jo on Dec 10, 2014 18:39:26 GMT -5
Yes, thx, works fine.
Btw, what's about my suggestion for a COMMENT3 in .Auto colorization ?
Jo
|
|
|
Post by George on Dec 11, 2014 13:42:14 GMT -5
Robert: Jo: I'll go to 3, but just because it ends in a number, please don't just assume going from 2 to 9 is simply a matter of altering some equate for the number allowed. For speed, the color parse/scan is carefully crafted to avoid loops. I'll look at doing it, but no promises.
George
|
|
|
Post by George on Dec 11, 2014 14:32:28 GMT -5
Robert: You nailed it, you're fully aware of how lazy I am, we argue over this stuff all the time. You ask for the full 'this is what *should* be done' version, and I whine about the effort involved or question just who will ever use all the features. I guess I'm still of the opinion that an awful lot of what we worked so hard to implement is just lying there totally unused. Creating more like that doesn't incent me to leap up and start coding. Several times now we've had a bug totally cripple a command for multiple releases before being fixed, and nobody even noticed. That's really a bummer. So adding COMMENT4 thru COMMENT9 sure smacks as one of the 'who will ever use it' type changes.
George
|
|
|
Post by Jo on Dec 11, 2014 17:40:28 GMT -5
Oh, I'm sorry to restart the COMMENT3 discussion in this wrong place. Should probably continue on the "Suggestions"-Board "More COMMENTn Definitions in Automatic Colorization File"-thread I started in January.
Jo
|
|
|
Post by George on Dec 12, 2014 11:42:14 GMT -5
Jo: No problem with the comments here. When I have news of any change, I'll pick up and update the other thread.
George
|
|