Messages

16

AGI Development Tools / Re: WinAGI 1.2.2 BETA

« on: January 17, 2018, 10:35:26 PM »

OK, so here's what I did.

1. I copied my old WinAGI install elsewhere.

2. I uninstalled it. (Guess I can skip these steps on a system that WinAGI isn't already installed on?)

3. I put the new exe and dll in a folder. Not in program files, just wherever the hell I wanted. I also copied the other files from the old install to the new folder.

4. I ran regsvr32 in an admin command prompt to register the dll.

5. I ran WinAGI.

And well, the saving bug is gone! But wait, there's more! I couldn't edit logics anymore, and when compiling the game I got errors about RichEditAGI.ocx. But don't worry, I just registered it too with regsvr32 (again as admin). Guess you just forgot to include this step, so maybe this will help someone.

Aaaand, I could edit logics normally, and the compiling bug I had encountered is gone. I guess it was related to the saving bug!

Making good progress here I think. I'll experiment and report back. Ironically, these fixes are kind of useless for me, as I don't really intend to do the developing on Windows 7 anyway, but who says fixing bugs is bad? You should have the least buggy software ever (everyone should) and maybe something else got fixed too. So yay.

17

AGI Development Tools / Re: WinAGI is Back

« on: January 16, 2018, 06:14:51 PM »

Sorry, when I said VB6 I meant the VB6 runtime. I don't usually think about the distinction at all because I have no use for Microsoft's dev tools, I don't like them even.

I don't believe the compiler warnings come up when compiling the test game under Windows XP. And, I would be surprised if your template game intentionally contains errors, anyway. WinAGI seems fairly well-made.

So weird how the save bug appears on Windows 7, but not XP or 10. How's that even happen!

18

AGI Development Tools / Re: WinAGI is Back

« on: January 15, 2018, 10:07:10 PM »

And thanks for getting back to me! On my Windows 98 PC I ran the Visual Basic 6.0 Runtime Plus installer that can be found on SourceForge to install VB6 on my PC. As it is, the installer for that had some strange errors, so maybe its claims of working on 95 and up aren't so true. I suspect that messed up the VB6 runtime, so I think I'll try again on a clean install, installing VB6 a different way, or try it on Windows ME instead. (I wanted to know about Windows 95 specifically, but if push comes to shove, I have successfully installed 98 on my DX2 before. Runs like a dog, but you can get stuff done alright. Oh, I might have screwed up the Windows installer service too. The runtime for that was pretty hard to find, thanks to Microsoft taking almost everything predating Windows 7 down! Well, thanks for letting me know that I'm not wasting my time here, it's probably me at fault here. (Oh, yeah, on the subject of what happens when running the executable... literally nothing. I open it and just stare at the desktop.)

In both cases, when I say compile, I mean recompiling the entire game. (Well, I would have to do that eventually if I wanted to release something, right? Maybe not...) But, now that you mention it, I should try compiling a logic too. (And well, I did on Windows 7. Appears to work as intended.) When I say not saving in picture and sound editors, I mean... the way it's supposed to work, is when you want to save, you close the window, and it asks if you want to save your work, right? That happens to me on Windows XP and Wine, but for some reason it just... doesn't on my Windows 7 PC. It just discards my work! (I haven't tried the view editor, but I should, shouldn't I...)

Oh, I was kind of wrong on how to save? Just noticed the resource menu. However, the save option is greyed out!

Well, here are the specific errors I got on Windows 7. I'm not sure if we can post links, and there doesn't seem to be a way to copy paste the error text... so I resorted to transcribing it:
Warning: 5025; Description: 'input_received' is normally a read-only flag; changing it could have unexpect results; Logic: 0; Line: 332; Module: MainLogic
Warning: 5025; Description: 'input_received' is normally a read-only flag; changing it could have unexpect results; Logic: 0; Line: 332; Module: MainLogic
Warning: 5025; Description: 'joystick_sensitivity_set' is normally a read-only flag; changing it could have unexpect results; Logic: 91; Line: 127; Module: Initalization
Warning: 5025; Description: 'input_received' is normally a read-only flag; changing it could have unexpect results; Logic: 99; Line: 161; Module: DebugHandler

Hope this post was coherent enough.

19

AGI Development Tools / Re: WinAGI is Back

« on: January 15, 2018, 03:23:13 PM »

Further information: I tried WinAGI on Wine again. There doesn't seem to be issues with saving per se, but I still can't compile anything, getting an error about WORDS.TOK being open. I guess the bug is something to do with the way files work slightly differently under Wine compared to Windows (because of them being different under Linux). Well, I doubt a bug that only happens under Wine because of Wine file weirdness matters much, so I guess I'll give up there.

And strangely enough (I just thought to test this) under Windows 7, compiling into an empty folder seems to work properly! (On the other hand, trying to compile into an empty folder just results in... an empty folder, on Wine. Weird.) Still has a bunch of weird errors, but the compiled template game appears to function as intended, just ScummVM recognizes it as an unknown game. It still appears that the picture and sound editors don't save right though. (Will have to look more into that...)

20

AGI Development Tools / Re: WinAGI is Back

« on: January 11, 2018, 12:24:26 PM »

Thank you for making WinAGI. I got it working on an old Windows XP computer, works alright, seems like a decent program. But when I use it on Windows 7, I get strange compiler errors when compiling the test game, and pictures and musics I create don't save. Strangely, iirc, this behaviour happens on Wine too. (Luckily there, QT AGI Studio at least seems to work as intended on modern distros, minus some display issues in the code editor.)

Is there something I'm doing wrong? If it works on Windows 10 for you, then why wouldn't it work on 7 for me? And if I can't get it working on 7 or Wine, then oh well, because...

Is it intended to work on Windows 95/98? Yes seriously. Why? Well, I was thinking it would be cool to make a game on an actual old DOS (/Windows 9x) PC. I tried getting it running on Windows 98 but nothing seems to happen at all, but I might have screwed up the VB runtime.