Sorry that our web page can bury the minor version number (the third digit).  We just put 6.0.5 on the site today, and have been changing some of the references to the minor version number.

If your About Curl tab of the Control Panel says that you have 6.0.4 installed, then that is what you have installed -- Except sometimes if you have a higher version installed, like 7.0, and do not have the 6.0 RTE currently running (if you have not previously run any 6.0 applets in this Curl session), then I think you might have to restart Curl to see Control Panel content updated.  I think that the 6.0 installer won't force the 7.0 RTE to be shutdown in this case.

So you would not have the 6.0.5 release unless you have manually downloaded and installed it.

Also, with regard to the Update tab of the Curl Control Panel, we do not always put out service packs on that update channel, and that update channel might not be changed at the same time that downloads are available at www.curl.com.  I think the idea is to not always push out service packs on the update channel unless the service pack concerns issues that would significantly impact a large number of users.

rshiplett wrote:

I should not that the manifest of the 603 Styles reads as follows (emphasis added)

 

 

{curl 6.0 manifest}

An applet with a header that said {curl 6.0.3+ applet} can use this manifest since it says 6.0 in the manifest header.  I'm actually not sure exactly what the rules are for compatibility between the applet header version and the manifest header version.  After a little testing, it seems that it might be that the applet header version will determine which RTE will be used out of the installed choices (possible multiple major versions, the highest major version will be used) and if any of them match the applet header, then the chosen RTE version will be matched against the versions listed in the manifest header when the manifest is loaded.  I looked around in the documentation without finding a place that explained how this is done.  Maybe someone else can be more authoritative.

The versions that you emphasize in the code below are actually meta-data, and those meta-data values are not involved with checking RTE version compatibility.  The meta-data values might be chosen to match some RTE versions if that is what you want to use as a coding convention, but that is an arbitrary choice.

{curl-file-attributes character-encoding = "windows-latin-1"}

{manifest COM.CURL.GUI.STYLED,

    version = "6.0"

}{component file DEFAULT-STYLE-SHEET,

    location = "default-style.scurl"

}

 

 

{component package COM.CURL.GUI.STYLED-CONTROLS,

    location = "skinned-controls/load.pcurl",

    version = "6.0"

}

 

 

|| only an issue if applet is declared as, say, 6.0.3+