Skip to main content

[archive] New XP Theme look

  • October 13, 2005
  • 25 replies
  • 0 views
D

[Migrated content. Thread originally posted on 03 October 2005]

At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

There is however a way you can get this new look.

Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
Which means, for our default runtime for instance, the file is stored as:
wrun32.exe.manifest.

For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

Finally, to get the new look, XP Theme must be enabled on your computer.

Attached to this message, you will find an archive (manifest.zip) containing three files.

V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

XP is of course a prerequisit to have this functionality.

    25 replies

    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    Thanks for the zip file!
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    Gisle,

    Included a screenshot with the manifest-file.
    My Radio-buttons and Check-boxes have normaly a Gray background and a White foreground.

    With the manifest-file the foreground-color changes in Black so there must still be something not working, or is it because I still don't use Runtime 7.0.
    1 Attachments
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    When you override system colors, e.g. use colors that differs from the system defaults, these are not being mapped.

    I would expect that changing your application colors to the standard system colors should address this.

    If not, a small reproduceable is always appreciated. If there is someting odd, I would like to know, so I appreciate this feedback.
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    How would you do this in an AcuThin environment?
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    Just the same, albeit instead of naming the manifest file wrun32.exe.manifest, you would name it acuthin.exe.manifest.
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    I try to use wrun32.exe.manifest and acuthin.exe.manifest and it is a nice discover see our application with XP graphic.

    Only one question.
    I see that the graphic do not change for the push button that have a bitmap. There is way to give to this button the same XP graphic?

    I attach one of my screen.

    Thx, bye

    Antonio Donato.
    1 Attachments
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    This is because they act a bit different from the normal buttons.
    We have the same issue with labels (can be workaround by setting to transparent) and radiobuttons, checkboxes that are displayed on tab controls. We are aware of this, but cannot promise any time for a fix yet.
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    I need some help on running the manifest through thin client. I am currently excuting acuthin.exe off of my local pc. When I rename wrun32.exe.manifest to acuthin.exe.manifest and try to execute windows wants to open it with another program. Not an executable. When I rename it to acuthin.exe I get the back DOS screen with nothing in it and the curser jumping around.

    Can anyone help?

    Thanks
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    I need some help on running the manifest through thin client. I am currently excuting acuthin.exe off of my local pc. When I rename wrun32.exe.manifest to acuthin.exe.manifest and try to execute windows wants to open it with another program. Not an executable. When I rename it to acuthin.exe I get the back DOS screen with nothing in it and the curser jumping around.

    Can anyone help?

    Thanks


    U have anyway to run acuthin.exe not acuthin.exe.manifest.
    Nedd only acuthin.exe.manifest to be present on the folder with acuthin.exe.

    Bye

    Antonio
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    I have added the manifest file to my application and am pleased with the XP look. However, I notice one anomaly- my status lines have disappeared.

    Is this a known problem? I am using the 7.2 runtime and compiler.
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    Hi,

    I think I've mentioned this before, or seen it reported elsewhere, but the manifest file doesn't work well with the title of frame, check-box and radio button controls when displayed on a tab control. I've attached an image showing the titles for frames and check-boxes which have a different background colour to other controls (e.g. text fields) on the screen. You'll have to trust me that radio buttons have the same problem.

    If you use these controls on screens without tab controls, then they display fine using the manifest file.

    The same problem will occur with text fields unless you specify the transparent property to be TRUE.

    Can you tell me if there is a solution in the pipeline for this problem? Will you be adding TRANSPARENCY to titles of frames, check-boxes and radio buttons?

    Ian
    1 Attachments
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    WaynePaulJ:
    I am not sure what you mean with status line disappearing, can you provide an illustration?

    Blacky:
    We do have these issues with the support for XP Visual Styles for consideration, but I cannot tell you any dates.
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    Has there been any update on the color of frames and other controls using the XP theme that are inside a tab control?
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    Support for XP Visual style support is scheduled and will appear in a future release.
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    As version 8.0 is the last version for Acucorp (ie until the Micro Focus version comes out) is the colour of controls on a Tab Control when using the manifest fixed or not?
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    Let me check this, I will come back to you.
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    As version 8.0 is the last version for Acucorp (ie until the Micro Focus version comes out) is the colour of controls on a Tab Control when using the manifest fixed or not?


    Allow me first of all to state one thing:
    There is not set a finit last version number of ACUCOBOL-GT.
    What I can say, is that version 8.0 is not the last one.

    Here is what scheduled as far as XP Visual styles regard:


      • Native controls (button, treeview, entryfield, etc...) will look XPish on XP and Vistaish on Vista. This is however configurable. You have to actively turn this on.
      • Themes are not supported.
      • The ACUCOBOL-GT tab control is not native, so I am afraid the problem with this one persists. I have not had a chance to test this though, I will test this when I have time.
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    Does Vista require a different manifest file to see the altered look or should it be activated with the same one that works in XP. Also are the Vista look changes active with the 7.0 runtime or only the 8.0?
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.

    1. Native Controls implementation in ACUCOBOL-GT is to be released in the next version.
    2. With no alteration (or Native Controls turned off in the next release) the application is using ComCtrl32 version 5 (classic control code and rendering). With an external manifest (or the next release) ComCtrl32 version 6 is in use. If you are on XP, then you get its ComCtrl32 version 6 with its code and visual rendering. If on Vista then it?s its ComCtrl32 version 6 with its code and visual rendering.
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    I tested v.8.0 runtime with the manifest and the runtime crashed. I got the message:
    "This application has failed to start because MFC80.DLL was not found. Re-installing the application may fix this problem."

    Does anyone knows anything about this problem?
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    Hi,

    I found this problem when Beta testing V8. Here's the reply I received from Tech Support at that time:-

    Hello Ian,

    On Windows XP our executable has an internal manifest that lists dependencies like MFC80.DLL. When using both internal and external manifests, such as in this case, the internal one is ignored and the external one is used. So if the external one has missing dependencies you will get the error you are getting. To resolve this you need to specify the missing dependencies in the external manifest. In attached file (fix.exe.manifest) should list all the dependencies the runtime needs. You will have to rename this file so that "fix" is the name of your executable and add anything else you need.

    Kind regards.
    Catherine Craig
    support@acucorp.com
    Customer Solutions Analyst


    I hope this helps you out :)

    The file mentioned is attached in ZIP format.

    Regards,

    Ian
    1 Attachments
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    Thank you very much Ian.
    The attached manifest works fine with the runtime v.8.0!

    Regards
    Adam
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    We are using 8.1.1 with native controls enabled and still the issue persists where checkboxes, radio sets and frame titles on tab controls still look goofy (i.e. no transparency). Does anyone know if this will ever be fixed or made to look better? Also on a side note, if you make labels transparent they go a grey color and look like they are disabled.
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    Does anybody know how to get the wrun32.exe.manifest working in Windows 7 using runtime 8.1.1?
    D

    [Migrated content. Thread originally posted on 03 October 2005]

    At the conference this year, several has inquired for the new XP Theme style, to give a more modern look.

    Due to compatibility issues, the ACUCOBOL-GT runtime has still not implemented the direct support for the new extended controls that ship with XP.

    There is however a way you can get this new look.

    Microsoft did by the time they released XP want to provide also existing applications with the new look, albeit, they realised some applications might not operate properly so they made the change dynamic. This was accomplished by introducing a technique that they refer to as a manifest.

    The manifest is present in form of a file, the file then is just a plain xml file which tells in details what controls the application supports.

    There has been a few issues with the new controls and ACUCOBOL-GT, but as of version 7 I believe we have them fixed.

    The trick with the manifest file is that it is named the same as the executable, except an additional extension is added; .manifest.
    Which means, for our default runtime for instance, the file is stored as:
    wrun32.exe.manifest.

    For the file to be functioning, it must be stored together with the runtime executable, e.g. in the directory which the wrun32.exe is.

    Finally, to get the new look, XP Theme must be enabled on your computer.

    Attached to this message, you will find an archive (manifest.zip) containing three files.

    V7old.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime without the manifest file.

    V7new.jpg, which is a print screen of the sample PrnDemoX application with the 7.0 runtime and the manifest file.

    Wrun32.exe.manifest which is the file to be stored along with the runtime to make it use the new XP look.

    XP is of course a prerequisit to have this functionality.
    I haven't tried our application under windows 7. But instead of using a manifest file, have you tried just setting the environment variable in your cblconfig file.

    WIN32_NATIVECTLS 1
    1 Attachments

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement