Menu

#270 File save bug (4.9.8.7)

open
nobody
None
9
2012-09-26
2004-03-20
Yury B.
No

When pressing CTRL+S to save a file it's often hangs or
crashes or simply doesn't save the editing file to disk
and the asterisk in the tab caption stays printed. Then
I close the tab and the programme asks to save the
modified file I say "Yes" and it closes the tab. Then,
when I reopen the file it doesn't contain the latest
changes!!! :(

When I select File->New->Resource then confirm "add to
project" and begin editing the file, save it and then
go on editing, it refuses to save it.

In general I experimented with saving and can't really
tell why and when it goes refusing to save or hangs. I
just can say it happens VERY OFTEN! :( So I'm affraid
to use dev-cpp as it may corrupt my sources!

Also, please, add "Save backup copy" option to the
editor settings.

I suspect CODE COMPLETION/CLASS BROWSER engine makes
many problems which possibly lead to bugs in saving
files to disk.

Thanks for your support and attention!

Discussion

  • Colin Laplace

    Colin Laplace - 2004-04-02

    Logged In: YES
    user_id=25510

    Could you please submit a sample project that I can try to
    reproduce the problem ? also please tell which library you
    installed (it is probably due to the class browser)

    Colin

     
  • Marek Januszewski

    Logged In: YES
    user_id=609236

    I found a way to reproduce second point of the bug description:
    1. start dev-cpp
    2. new project - choose windows application
    3. save all
    4. file->new->resource file
    5. type something (// and enter or sth)
    6. save all
    7. type some more in resource file (like another // and enter)
    8. save all
    now newly modified rc file is still modified (has asterisk
    next to the name), but doesn't save.

    The problem is in:
    function TProjUnit.Save: boolean;
    the file doesn't fall into either "ifs" - doesn't have
    fEditor and FileExists.

    Colin: the below solves the problem but please review it:
    instead of:
    --
    function TProjUnit.Save: boolean;
    ...
    fEditor.New := False;
    fEditor.Modified := False;
    fEditor.Close;
    fEditor:= nil;
    end
    else
    --
    I'm not sure why the fEditor is destroyed. If we kept it it
    would solve the problem:
    --
    fEditor.New := False;
    fEditor.Modified := False;
    Editor := fEditor;
    end
    else
    --
    please review it.

     
  • Colin Laplace

    Colin Laplace - 2004-04-06

    Logged In: YES
    user_id=25510

    fixed, the second part of the bug, it was a problem with
    uninitialized editor.
    For the first part of the bug report, I would really need a
    sample project in order to reproduce it

    Greetings,
    Colin

     
  • Marek Januszewski

    Logged In: YES
    user_id=609236

    has this been fixed in 4.9.9.2?

     

Log in to post a comment.