1
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
I've made an improvement to NewRisingSun's GAL decompiler to allow sysdefs like:Code: [Select]%var menaceIsHere 103 ALL
This means that menaceIsHere is generally the name of variable 103, except in room 21, where it is called witchGrabbed. This is useful because of the crowded variable space in both GAL and AGI. Something to consider?
%var witchGrabbed 103 21
(I don't think menaceIsHere is a good general name anymore, btw - its uses are far too varied)
WinAGI v2.x wont open a project if the wag states it's v3, but changing back to 2.3 allows it to open again. I assume things would break if you've updated the extended characters in logics. Otherwise, are v2 and v3 projects really incompatible or does WinAGI 2 just not expect a version 3 to be valid?As of right now the change in extended character support is the only incompatibility. Changing the version property back to 2.3 is the correct way to revert the WAG file.
I was wanting to take a look at the code. NuGet provides the dependencies. I did get it to retrieve the FastColorBoxes package, but not Microsoft.VisualStudio.OLE.Interop nor NAudio.Yeah, I remember now - NuGet is for managing libraries and such that you can add to your projects. It's been a while since I have had to deal with that. Weird that those two won't load.
graphics.DrawString("Hello world!", someFont, Brushes.Black, rectangle)
Most of their examples are no better than a 'Hello World' which doesn't help understand details and nuances.
I am having trouble with the NuGet packages. I have never had a problem with them before. It is throwing 404 errors for all three of the packages.I'm not sure what you are referring to. Are you talking about the release installation files? There's only two - setup.exe and WinAGI.Installer.msi. If you're having trouble downloading I can provide a shared file link.
Cool to finally get a look at the new version. I see the logic files need to be updated if they use extended characters. Was that a significant change?Not really. In the current version, I chose to store all characters as single bytes, reading the bytes as the desired DOS code page when loading. This seemed like a good idea until I realized it required a lot of extra code to manage cutting and pasting.
Having done graphics editors in both VB Classic and C#, I can tell you this much: it's not that hard to use System.Drawing.
Strange they didn't use the most recent interpreter version.The amount of free memory (heap space) is actually slightly smaller in v2.936 and all thee v3 interpreters (except v3.002.149, which gained a few bytes by dropping string storage from 24 to 12). So unless you really need the few commands added in v2.936 and/or v3, you actually get a few more bytes of available heap space by using 2.917. In AGI, 'a few bytes' can be a LOT of memory.
SMF 2.0.19 |
SMF © 2021, Simple Machines
Simple Audio Video Embedder
Page created in 0.04 seconds with 20 queries.