Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ TheIDE » U++ TheIDE: Other Features Wishlist and/or Bugs » Confusing compile-defaults
Confusing compile-defaults [message #5434] Thu, 21 September 2006 15:24 Go to next message
piotr5 is currently offline  piotr5
Messages: 107
Registered: November 2005
Experienced Member
recent versions of u++ show a confusing behaviour: changing general compile-options does not propagate to the current project, one does need to change the individual project's settings for "Shared" and "Blitz". with Blitz it would be easy to add the functionality that a grey square does indicate that the general default-options should be used, and similarily the choice between shared and static could be set to un-checked (and made un-checkable) since it's a radio-button.

therefore my feature-request. experienced users might have no problem with the current behaviour, but for beginners it might be confusing that changed options do not show effect in the currently open project! I propose that the compiler-settings in the settings-menu should stay as they are, and the settings in the compile-menu should by default have disabled all Shared vs static settings, and a grey square at the choice for Blitz, in both: debug and release-version. now it isn't even possible to switch Blitz (the option which is applied to all sub-projects) into a greened square, even less to remove the selected-property from all radio-buttons concerning shared vs static!
Re: Confusing compile-defaults [message #5443 is a reply to message #5434] Thu, 21 September 2006 21:39 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 13975
Registered: November 2005
Ultimate Member
The options are "copied" from build method when opening the main package for the first time. Is your observation consistent with this or something does not work?
Re: Confusing compile-defaults [message #5510 is a reply to message #5443] Thu, 28 September 2006 15:03 Go to previous message
piotr5 is currently offline  piotr5
Messages: 107
Registered: November 2005
Experienced Member
Yes, no problem here. it was just meant as a feature-request.
Previous Topic: Is MT-option broken now?
Next Topic: Mark selection with t_ (609_dev3)
Goto Forum:
  


Current Time: Fri Apr 19 13:19:26 CEST 2024

Total time taken to generate the page: 2.02170 seconds