Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
CHAIN command not working
#9
That's exactly how QB64 handles CHAIN. Common Shared variables are basically saved to the drive when the program hits chain, and then they're loaded from the drive when the second program starts. It's really rather old school and quite clunky and inefficient, and I'd honestly suggest that instead of using CHAIN for sharing such chunks of data, one would be better off to simply write and clean up a data file themselves. By writing your own data to disk, you have more control over it -- when it gets written to, when it gets deleted, how you store it, if you decide to compress it, ect, ect.

My personal advice is to just pretend that CHAIN doesn't exist. If you need to share values, do so with your own data file -- don't rely on the clunky system which QB64 has implemented in place to do it for you. Wink
Reply


Messages In This Thread
CHAIN command not working - by TerryRitchie - 08-08-2022, 04:02 AM
RE: CHAIN command not working - by bplus - 08-08-2022, 03:00 PM
RE: CHAIN command not working - by mdijkens - 08-08-2022, 03:28 PM
RE: CHAIN command not working - by mnrvovrfc - 08-08-2022, 10:47 PM
RE: CHAIN command not working - by Kernelpanic - 08-08-2022, 04:04 PM
RE: CHAIN command not working - by TerryRitchie - 08-08-2022, 08:07 PM
RE: CHAIN command not working - by Kernelpanic - 08-08-2022, 08:56 PM
RE: CHAIN command not working - by TerryRitchie - 08-08-2022, 09:25 PM
RE: CHAIN command not working - by SMcNeill - 08-08-2022, 11:34 PM
RE: CHAIN command not working - by Pete - 08-09-2022, 06:09 AM
RE: CHAIN command not working - by TempodiBasic - 08-12-2022, 05:35 PM
RE: CHAIN command not working - by TempodiBasic - 09-01-2022, 12:13 AM
RE: CHAIN command not working - by Udix - 11-01-2022, 01:31 PM



Users browsing this thread: 15 Guest(s)