$EMBED: Revision history

24 March 2024

• curprev 09:4309:43, 24 March 2024‎ RhoSigma talk contribs‎ 4,618 bytes +45‎ No edit summary

19 February 2024

• curprev 14:3314:33, 19 February 2024‎ RhoSigma talk contribs‎ 4,573 bytes +3‎ No edit summary

16 January 2024

• curprev 16:5316:53, 16 January 2024‎ RhoSigma talk contribs‎ 4,570 bytes +52‎ No edit summary
• curprev 16:5016:50, 16 January 2024‎ RhoSigma talk contribs‎ 4,518 bytes −12‎ No edit summary

15 January 2024

• curprev 00:2200:22, 15 January 2024‎ RhoSigma talk contribs‎ 4,530 bytes +359‎ No edit summary

14 January 2024

• curprev 23:4723:47, 14 January 2024‎ RhoSigma talk contribs‎ 4,171 bytes +229‎ No edit summary

3 January 2024

• curprev 12:5812:58, 3 January 2024‎ RhoSigma talk contribs‎ 3,942 bytes +308‎ No edit summary

19 December 2023

• curprev 08:1408:14, 19 December 2023‎ RhoSigma talk contribs‎ 3,634 bytes +292‎ No edit summary

16 December 2023

• curprev 09:1609:16, 16 December 2023‎ RhoSigma talk contribs‎ 3,342 bytes +13‎ No edit summary

15 December 2023

• curprev 00:1500:15, 15 December 2023‎ RhoSigma talk contribs‎ 3,329 bytes +48‎ No edit summary
• curprev 00:0200:02, 15 December 2023‎ RhoSigma talk contribs‎ 3,281 bytes +3,281‎ Created page with "The '''$EMBED''' metacommand can embed any designated file (e.g. images, sounds, fonts and all other file types) into the compiled EXE file. You can roughly compare this to converting and placing a file's contents into DATA lines, but '''$EMBED''' obviously is much more convenient. {{PageSyntax}} : $EMBED:'{{Parameter|filename}}','{{Parameter|handle}}' {{PageParameters}} ; IMPORTANT : *Both parameters must be enclosed in single quotes and given as literal str..."