Watch, Follow, &
Connect with Us
Public Report
Report From: Delphi-BCB/IDE/Dialogs/Project Options    [ Add a report in this area ]  
Report #:  99275   Status: Closed
Changes to All Configurations - All Platforms are not applied to all configurations/platforms
Project:  Delphi Build #:  16.0.4256.43595
Version:    16.0 Submitted By:   Dalija Prasnikar
Report Type:  Basic functionality failure Date Reported:  9/24/2011 3:44:49 AM
Severity:    Critical / Show Stopper Last Updated: 5/27/2012 11:41:56 PM
Platform:    All platforms Internal Tracking #:   287857
Resolution: As Designed (Resolution Comments) Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: No Ratings Yet
0.00 out of 5
Total Votes: 20
Description
When you change some settings in Project Options dialog under Target: All Configurations - All Platforms you would expect that this change will be applied to all configurations and platforms, but it is not so.

There are some serious bugs in Project Options Dialog, I have described few in the steps, but there may be others. There are many options and it is very time consuming if you need to recheck every change you have made. Project Options should work flawlessly.
Steps to Reproduce:
1. Create new VCL application project
2. Open Project Options
3. Open Application Settings
4. Select Target - All configurations - All platforms
5. Load new icon to the project - Select Copy icon to the project's directory changing the name to...
6. Under Runtime themes select Use cusom manifest and load your custom manifest
7. Change Target to All configurations - 32 bit Windows platform - Icon is there, but manifest is not
8. Change Target to Debug configuration - All platforms - Icon is there, so is the manifest
9. Change Target to Debug configuration - 32 bit Windows platform - Icon is not there, manifest is not there
10. Change Target to Release configuration - All Platforms - Icon is there, manifest is there
11. Change Target to Release configuration - 32-bit Windows platform - Icon is there, manifest is not there

I didn't check how it behaves for Windows 64 bit and OSX settings

12. Go to Version Info settings
13. Select Target - All configuration - All platforms
14. Change Language to something else
15. Change Target - All configurations - 32 bit windows platform - language is not changed.
Workarounds
None
Attachment
None
Comments

Dalija Prasnikar at 12/5/2011 4:09:11 AM -
Closed as Designed, you got to be kidding.

If I can set something under All Configurations - All Platforms I expect that setting to be propagated to nothing less than All Configurations - All Platforms. If something cannot be propagated for whatever reason than please disable that setting in the first place.

Tomohiro Takahashi at 12/5/2011 5:01:21 PM -
This is a comment from internal tracking system.
<<<<<<<
This is the way the inherites works in project options.  When the application is created the default manifest that enables runtime themes is added to the win32 configuration.  You change the base configuration to a custome manifest.  The items the inherite there options from the base get the new manifest, but the ones that inherit from win32 get the win32 ones.  We were looking at cleaning this inherits up, but we do not beleve that will happen now.
>>>>>>>

Markus Humm at 12/12/2011 2:25:07 PM -
Hi,

with this in mind: "but we do not beleve that will happen now." the report should have been "dereferred to next release" rather than closed this way!

Greetings

Markus

Dalija Prasnikar at 12/6/2011 2:00:14 AM -
Thanks, for the info.

I think this report shoul be reopended, because there is a real problem. When and how it could be fixed is another matter.

Jessie Potts at 3/28/2012 4:11:09 PM -
This is still an issue in build #16.0.4429.46931.  However, I found that I can eliminate the problem by opening the project's "dproj" file and delete all of the <VerInfo_Keys> tags *except* for the base property group (<PropertyGroup Condition="'$(Base)'!=''">).  Doing this allows the version information to be inherited to the different build and platform configurations.

Frederik Slijkerman at 5/9/2012 7:47:54 AM -
I think the Delphi developer handling this issue didn't realize that it also applies to version information. This is really a huge problem, see:
http://stackoverflow.com/questions/8048716/how-to-manage-version-information-on-delphi-xe2-across-platforms

Is there any way to re-open this issue?

Ján Kolár at 5/25/2012 1:52:27 AM -
This problem is not solved even in Update4 Hotfix 1 (16.0.4504.48759). Please fix it, its really annoying wasting time when converting project from XE to XE2.

Tomohiro Takahashi at 5/26/2012 7:27:44 PM -
This report was closed as 'As Designed'.

CK Dev at 12/18/2012 11:58:11 PM -
This is a big problem for me too.

I am about to ship 120 DLL's with no version information, because I just don't have the manpower to sit and edit them all.

Isn't Delphi supposed to allow one developer to do the work of 20? This is NOT the Delphi way!

PS. I just edited one DLL, set all the settings IDENTICAL via going back and forth and copying and pasting. I then incremented the build number. It doesn't propogate either! So every release I am going to have to do this all over again!

Van Swofford at 10/11/2012 12:46:19 PM -
But it is obvious that it is not as designed, unless it was designed to be broken.

Server Response from: ETNACODE01