I just clicked the [X] in the upper right corner,
and the editor is still open, but the main part of
the window is all white.
All of the tabs disappeared.
There were no files that needed to be saved.
The menu seems to work, but I'm afraid to do anything.
So I did a File Exit, and it quit.
I started the Editor up again and it seems fine now.
I clicked the [X] and it quit normally.
Attached is a screen shot.
This was in version 16.20 Actual 64-bit.
.
Potential Bug Closing Editor
Potential Bug Closing Editor
- Attachments
-
- rjtesnap58.png (34.51 KiB) Viewed 5323 times
RJTE version 16.36 (Actual) - 64-bit
Win 10 Pro 64-bit 8 GB RAM Intel Core i7-6700 3.40 GHz SCSI Hard Drive 1 TB
Note: The signature is dynamic, not static,
so it may not show the correct version above
that was in use at the time of the post.
Win 10 Pro 64-bit 8 GB RAM Intel Core i7-6700 3.40 GHz SCSI Hard Drive 1 TB
Note: The signature is dynamic, not static,
so it may not show the correct version above
that was in use at the time of the post.
- Rickard Johansson
- Site Admin
- Posts: 6783
- Joined: 19 Jul 2006 14:29
Re: Potential Bug Closing Editor
Next time please send me the <AppData>\Roaming\RJ TextEd\Data\DebugOutput.txt file as well.
Re: Potential Bug Closing Editor
That file doesn't exist right now. When is it created?
RJTE version 16.36 (Actual) - 64-bit
Win 10 Pro 64-bit 8 GB RAM Intel Core i7-6700 3.40 GHz SCSI Hard Drive 1 TB
Note: The signature is dynamic, not static,
so it may not show the correct version above
that was in use at the time of the post.
Win 10 Pro 64-bit 8 GB RAM Intel Core i7-6700 3.40 GHz SCSI Hard Drive 1 TB
Note: The signature is dynamic, not static,
so it may not show the correct version above
that was in use at the time of the post.
- Rickard Johansson
- Site Admin
- Posts: 6783
- Joined: 19 Jul 2006 14:29
Re: Potential Bug Closing Editor
You should find a "DebugOptions.txt file in your program folder. Modify it and save.
E.g.
; DebugOutput
; 0 = No output
; 1 = Output to log file <AppData>\RJ TextEd\Data\DebugOutput.txt
; 2 = DebugOutputString. Use e.g. DebugView to display the output
DebugOutput=1
; LogFileAppend
; 0 = No append. Allways create a new log file at startup.
; 1 = Append. Append new debug data to old ones. NOTE! The file may become very large!
LogFileAppend=0
E.g.
; DebugOutput
; 0 = No output
; 1 = Output to log file <AppData>\RJ TextEd\Data\DebugOutput.txt
; 2 = DebugOutputString. Use e.g. DebugView to display the output
DebugOutput=1
; LogFileAppend
; 0 = No append. Allways create a new log file at startup.
; 1 = Append. Append new debug data to old ones. NOTE! The file may become very large!
LogFileAppend=0
Re: Potential Bug Closing Editor
I edited that file, and it wouldn't let me save it, and asked me
if I wanted to open the Editor in "Administrator Mode",
or something like that, so I did, and the Editor restarted,
but all my open files disappeared, which I hoped would come back
when I quit and restarted the Editor, so I opened the file again
and edited it and saved, and quit the Editor,
and started it up again normally, and
all of my open files went away permanently,
WHICH IS EXTREMELY ANNOYING.
Now I've lost all my file and work context.
I can kind of get it back opening recently edited files.
if I wanted to open the Editor in "Administrator Mode",
or something like that, so I did, and the Editor restarted,
but all my open files disappeared, which I hoped would come back
when I quit and restarted the Editor, so I opened the file again
and edited it and saved, and quit the Editor,
and started it up again normally, and
all of my open files went away permanently,
WHICH IS EXTREMELY ANNOYING.
Now I've lost all my file and work context.
I can kind of get it back opening recently edited files.
RJTE version 16.36 (Actual) - 64-bit
Win 10 Pro 64-bit 8 GB RAM Intel Core i7-6700 3.40 GHz SCSI Hard Drive 1 TB
Note: The signature is dynamic, not static,
so it may not show the correct version above
that was in use at the time of the post.
Win 10 Pro 64-bit 8 GB RAM Intel Core i7-6700 3.40 GHz SCSI Hard Drive 1 TB
Note: The signature is dynamic, not static,
so it may not show the correct version above
that was in use at the time of the post.
- Rickard Johansson
- Site Admin
- Posts: 6783
- Joined: 19 Jul 2006 14:29
Re: Potential Bug Closing Editor
Fixed the reopen file issue.
I think I've said it before, but sessions are very useful. You can have any number of working environments (sessions) and each session can contain as many files as you want.
I use sessions a lot myself...
I think I've said it before, but sessions are very useful. You can have any number of working environments (sessions) and each session can contain as many files as you want.
I use sessions a lot myself...
Re: Potential Bug Closing Editor
Right, but before the current version editor would re-open unsaved files with their content and state untouched, hence there wouldn't be any need for a session (can it handle unsaved files? I don't think so). Yesterday I had the same experience as rjbill, I restarted the editor in admin mode and two my unsaved files were gone (luckily, I made no important edits).
Alium tibi quaere fratrem; hic, quem tuum putas, meus est. Titus Flāvius Caesar Vespasiānus Augustus
- Rickard Johansson
- Site Admin
- Posts: 6783
- Joined: 19 Jul 2006 14:29
Re: Potential Bug Closing Editor
It works with both unsaved and delay opened files, in the next version...
Re: Potential Bug Closing Editor
I can't find any information on sessions in Help.
I just made one with all of my current documents and called it "Primary".
I don't plan on closing the session, just hopefully not lose context anymore.
So it's kind of like a perpetual session.
Does it automatically update the Session when I close and open files?
Do I have to manually SAVE to make sure nothing is lost?
Does it update the session automatically as I work, or when I exit the editor?
I just made one with all of my current documents and called it "Primary".
I don't plan on closing the session, just hopefully not lose context anymore.
So it's kind of like a perpetual session.
Does it automatically update the Session when I close and open files?
Do I have to manually SAVE to make sure nothing is lost?
Does it update the session automatically as I work, or when I exit the editor?
RJTE version 16.36 (Actual) - 64-bit
Win 10 Pro 64-bit 8 GB RAM Intel Core i7-6700 3.40 GHz SCSI Hard Drive 1 TB
Note: The signature is dynamic, not static,
so it may not show the correct version above
that was in use at the time of the post.
Win 10 Pro 64-bit 8 GB RAM Intel Core i7-6700 3.40 GHz SCSI Hard Drive 1 TB
Note: The signature is dynamic, not static,
so it may not show the correct version above
that was in use at the time of the post.