From 74b95f776ef512743852f3c96e71f127efd65adf Mon Sep 17 00:00:00 2001 From: Greg Kepler Date: Fri, 8 Sep 2017 16:14:33 -0400 Subject: [PATCH] [docs] Fixed html markup error in the resources guide. --- docs/htmlsrc/guides/resources/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/htmlsrc/guides/resources/index.html b/docs/htmlsrc/guides/resources/index.html index c835c56130..8205e09eee 100644 --- a/docs/htmlsrc/guides/resources/index.html +++ b/docs/htmlsrc/guides/resources/index.html @@ -118,7 +118,7 @@

Using a Resource

Resources on Windows

Let's take a look now at how resources are handled on Microsoft Windows. The most noticeable difference relative to OS X is that resources are not stored as individual files, since an EXE does not encapsulate a directory like an OS X application bundle does. Instead, resources are baked into the EXE using a resource compiler, and are stored as binary data. However we can access this binary data in memory using the same loadResource() routine we do on OS X. Furthermore, Cinder's internal code is able to handle loading from either the flat file or in-memory representations transparently and efficiently, so in general you will not need to change application code between the platforms.

- Note:

The text which follows is helpful for understanding how Windows resources work under the hood, but we recommend you read and consider the alternative techniques under the Cross-Platform Resources section as well, even if you are writing Windows-only code.

+

Note: The text which follows is helpful for understanding how Windows resources work under the hood, but we recommend you read and consider the alternative techniques under the Cross-Platform Resources section as well, even if you are writing Windows-only code.

Adding a Resource