Menu ▾ ▴

#458 Need Settings->Save Settings

Next_Release
invalid
Teodor Petrov
None
Bug_Report
2017-01-02
2016-12-23
W Sforge
No

I think there is a bug where you change your settings under the settings menu and then you close codeblocks thinking your settings are saved, but instead they are lost because your didn't modify your project workspace list and click File->save projects.

I think the best way to solve this problem is just to add another option under settings to save the profile settings. Example:

Settings->Save Settings

Related

Tickets: #458

Discussion

  • W Sforge

    W Sforge - 2016-12-23

    The reason I'm reporting this is because i was trying to setup multiple "profiles" using --profile command line option to support different linker/cflag targets...and realized that I need to mess around with adding and deleting files in workspace manager to get the project settings to save ...
    just feel... that's kind of painful... would be nice to just have a save profile opion under settings to make it fast and easy...

     

    Last edit: W Sforge 2016-12-23

  • bluehazzard

    bluehazzard - 2016-12-25

    And again, what are you doing? Why do you use codeblocks/global configuration to configure your project

    Anyway: Can you give us exact steps how to reproduce this. Global Settings (all settings under the Settings menu) are always stored at program exit.... If they are not stored correctly then the problem is mostly a problem with write access on the config file

     

  • Teodor Petrov

    Teodor Petrov - 2016-12-26
    • status: open --> invalid
    • assigned_to: Teodor Petrov
     

  • W Sforge

    W Sforge - 2016-12-30

    Don't you think its kind of bad to not give the user a chance to save his global settings profile at will? What happens if the power goes out or the program crashes while debugging some code? then all your compiler flags will be lost because you didn't exit the problem to save your global profile.
    (I noticed that there is an auto-save feature that is off by default which is ironically stored in the global settings that is not getting saved and is off by default...) but i think auto-save is still kind of bad...because your program can still crash in between autosaves based on a periodic time interval.
    All you need to do is just add "save profile" under the settings menu item... so that people can have that feel good feeling that you get when you press the "cross road button" when crossing at a busy intersection... you don't know if it working, but damn is it satisfying.

    QUESTION: And again, what are you doing? Why do you use codeblocks/global configuration to configure your project

    ANSWER: In order to configure C-Flags and Libs for the project. I have two project at the moment. One that uses native windows API and DLL's and another that is using "MSYS2/pkg-config gtkmm-3.0". to get around this problem. I started using the command line switch to codebock "--profile". Thus, now I have two global profiles with diferent C-Flags and Libs.

    QUESTION: Anyway: Can you give us exact steps how to reproduce this. Global Settings (all settings under the Settings menu) are always stored at program exit.... If they are not stored correctly then the problem is mostly a problem with write access on the config file

    ANSWER: The way I found the problem was a follows:.
    (1) start codeblocks from command line: "codeblocks --profile=gtkmm3"
    (2) try to add gtkmm specific c-flags and libs under Settings->Compiler
    (3) exit codeblocks
    (4) start codeblocks from command line: "codeblocks --profile=wincypto"
    (5) try to add windows specific c-flags and libs under Settings->Compiler
    (6) exit codeblocks
    (7) start codeblocks from command line: "codeblocks --profile=ask"
    (8) click on gtkmm3 profile
    (9) open settings->compiler and observe that c-flags and libs are not set correctly and the profile was not save for gtkmm3 profile.

    The way I got this to work and save the profiles was by opening a project and screwing around with deleteing and adding files to the project again and then saveing the project and close codeblocks...

    If this works for you then there is something intermitten going on where it works sometimes saves the profile and sometimes it doesn't.

     

    Last edit: W Sforge 2016-12-30

    • W Sforge

      W Sforge - 2016-12-30

      that sounds like what i was seeing.

      On Fri, Dec 30, 2016 at 6:13 AM, W Sforge wsforge@users.sf.net wrote:

      Don't you think its kind of bad to not give the use a chance to save him
      profile as will? What happens if the power goes out or the program crashes
      while debugging some code? then all your compiler flags will be lost
      because you didn't exit the problem to save your global profile.

      QUESTION: And again, what are you doing? Why do you use codeblocks/global
      configuration to configure your project

      ANSWER: In order to configure C-Flags and Libs for the project. I have two
      project at the moment. One that uses native windows API and DLL's and
      another that is using "MSYS2/pkg-config gtkmm-3.0". to get around this
      problem. I started using the command line switch to codebock "--profile".
      Thus, now I have two global profiles with diferent C-Flags and Libs.

      QUESTION: Anyway: Can you give us exact steps how to reproduce this.
      Global Settings (all settings under the Settings menu) are always stored at
      program exit.... If they are not stored correctly then the problem is
      mostly a problem with write access on the config file

      ANSWER: The way I found the problem was a follows:.
      (1) start codeblocks from command line: "codeblocks --profile=gtkmm3"
      (2) try to add gtkmm specific c-flags and libs under Settings->Compiler
      (3) exit codeblocks
      (4) start codeblocks from command line: "codeblocks --profile=wincypto"
      (5) try to add windows specific c-flags and libs under Settings->Compiler
      (6) exit codeblocks
      (7) start codeblocks from command line: "codeblocks --profile=ask"
      (8) click on gtkmm3 profile
      (9) open settings->compiler and observe that c-flags and libs are not set
      correctly and the profile was not save for gtkmm3 profile.

      The way I got this to work and save the profiles was by opening a project
      and screwing around with deleteing and adding files to the project again
      and then saveing the project and close codeblocks...

      If this works for you then there is something intermitten going on where
      it works sometimes saves the profile and sometimes it doesn't.

      Status: invalid
      Milestone: Next_Release
      Created: Fri Dec 23, 2016 05:14 PM UTC by W Sforge
      Last Updated: Mon Dec 26, 2016 03:54 PM UTC
      Owner: Teodor Petrov

      I think there is a bug where you change your settings under the settings
      menu and then you close codeblocks thinking your settings are saved, but
      instead they are lost because your didn't modify your project workspace
      list and click File->save projects.

      I think the best way to solve this problem is just to add another option
      under settings to save the profile settings. Example:

      Settings->Save Settings

      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/codeblocks/tickets/458/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       

      Related

      Tickets: #458

      alternate

  • Teodor Petrov

    Teodor Petrov - 2017-01-02

    You're doing it wrong.

    The settings for gtkmm3 and wincypto should be in the project and not in the global compiler settings!
    Use separate targets and switch between them when you need to use one or the other.
    There is no point to use profiles for this, they are not designed to solve this problem!

     

Log in to post a comment.

mdb logo