#57 save on deactivate misses most files

Feature_Request
closed-out-of-date
SciTE (625)
3
2005-02-18
2002-08-09
No

The Save on Deactivate feature apparently tries to
save only the current file. It would seem that the
whole point of this feature is that the programmer
wants to make sure when he switches to another
window that all files are saved, so I think this is a bug.

Running SciTE 1.46 on Windows 98 SE.

Discussion

  • Neil Hodgson

    Neil Hodgson - 2002-08-10
    • milestone: 100660 --> Feature_Request
    • assigned_to: nobody --> nyamatongwe
    • priority: 5 --> 3
     
  • Neil Hodgson

    Neil Hodgson - 2002-08-10

    Logged In: YES
    user_id=12579

    Works as documented. Contributions welcome.

     
  • Neil Hodgson

    Neil Hodgson - 2003-10-21

    Logged In: YES
    user_id=12579

    Now saves all buffers with file names.

     
  • Neil Hodgson

    Neil Hodgson - 2003-10-21
    • status: open --> closed-accepted
     
  • Peter Hansen

    Peter Hansen - 2003-11-30

    Logged In: YES
    user_id=567267

    I believe the support for this is broken in v1.57, although it
    seems to work in v1.56. With save.on.deactivate=1 and
    check.if.already.open=1 I get the following error. (I can
    create a new bug report if you wish, or recreate using
    scite.exe instead of sc1.exe).

    SC1 caused an invalid page fault in
    module SC1.EXE at 0167:0040109e.
    Registers:
    EAX=00000000 CS=0167 EIP=0040109e EFLGS=00010246
    EBX=006cd79c SS=016f ESP=006cd5b8 EBP=006cd5dc
    ECX=006cd79c DS=016f ESI=00000000 FS=542f
    EDX=7efefeff ES=016f EDI=00000000 GS=2ea7
    Bytes at CS:EIP:
    8b 46 04 85 c0 76 24 3b f8 77 20 8b 06 85 c0 74
    Stack dump:
    006cd788 0040aa0f 006cd788 00000140 00000140 00000000
    006cd788 00000000 00000000 006cd614 0040b64b 006cd788
    00000140 006cd614 00000140 0040e076

     
  • Peter Hansen

    Peter Hansen - 2003-11-30
    • status: closed-accepted --> open-accepted
     
  • Neil Hodgson

    Neil Hodgson - 2003-12-01

    Logged In: YES
    user_id=12579

    I have seen a crashing bug somewhat similar to this but it
    is not simply a matter of turning on save.on.deactivate and
    check.if.already.open and getting crashes. I haven't seen it
    again and it woul be good to have a consistently
    reproducible case.

     
  • Neil Hodgson

    Neil Hodgson - 2005-02-18
    • status: open-accepted --> closed-out-of-date
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks