Quote from: SeaVipe on February 09, 2018, 10:04:36 PMThanks.Similar in syntax to a Metacommand?'$Include - Alternate form of the #include directive.'$Dynamic - Alternate form of the Option Dynamic statement.'$Static - Alternate form of the Option Static statement.'$Lang - Alternate form of the #lang directive.Yes, that's basically correct. I could have called it anything but chose to use '#RESOURCE. Hopefully that doesn't become confusing to users.
Thanks.Similar in syntax to a Metacommand?'$Include - Alternate form of the #include directive.'$Dynamic - Alternate form of the Option Dynamic statement.'$Static - Alternate form of the Option Static statement.'$Lang - Alternate form of the #lang directive.
To be honest, in most cases a WinFormsX application will be created using a visual designer through a WinFBE project. When part of a WinFBE project, the resource will be identified as such and will be automatically part of the project compile. There would be zero need for the directive in those cases.In the short one file examples that I have posted to test WinFormsX features, I use the directive in order to make compiling a little easier (not having to add it to WinFBE's compiler options). It also saves me from having to create a formal project for every code example.