Posts by cimics

Well, I'm not paying for it. My ISP gives it to me for free.

I saw that elsewhere, and my numbers were being figured as floats. Hence sometimes rounding to the tenths decimal place. What I had forgotten is that MMF only recognizes 6 significant figures. So when the numbers got large enough, the decimals would just start to disappear with the next t place being rounded. Once I realized that was what was happening, I started looking for an extension to do floats and then, lo and behold, the double-precision object does that. And since I have the pro version, I have it. It has actually been working quite well.

I figured out that Fusion only recognizes 6 significant digits, and that was the problem. So now I've found the double precision object (I have 2.5+ pro version), and it looks like it's going to do the trick.

I am trying to create a program that calculates money. But every time I multiply two numbers together, it rounds to the tenths place (or sometimes, a whole number) even though there are more decimals than the tenths place. Add numbers together and it's fine. But multiply them together and it rounds to the nearest tenths place. I even tested this out by multiplying two constants together with two decimal places each and the result was displayed as rounded to the nearest tenths place. I have tried this a number of ways. Global values, counters, strings, and multiplying by 1.0 or adding 1.0 and nothing seems to work. It is rendering a floating point number, but with only one decimal place, when I want (at least) two.

I figured out F-Secure is doing it. I made an exception to the real time scanning and now there is no delay in the application starting up. But this still means I have to make an exception every time I build an app with a new name, and that's just for my computer. F-Secure doesn't say it's a virus and doesn't stop it, but it does take it's sweet time analyzing it before allowing it to run. Is there something I can tweak in the application to avoid that? And in any event, something in the recent build (or one of the fairly recent builds) is causing this.

I tried to report this in the bug reporting system, but it says it is down for maintenance.

I have version 2.5+ with the latest official release patch. It had been awhile since I had built something, and I found out to my dismay that it took FOREVER for a built application to load. The application doesn't appear to be hanging because when I start up task manager, it's NOT THERE. But eventually, it loads and then it shows up in task manager. If I try to delete the app (after it has loaded and I closed out of it), I get a message saying F-Secure (the antivirus program) is messing with it somehow. But if I wait long enough, I can delete it. I fiddled around with the application making no progress. So I decided to test this with a TOTALLY BLANK application. Same thing happens. So now I can't build anything without this happening. Fusion apps I had earlier built, including some on 2.5, work fine. So I don't know if this is something in the latest Fusion update or if it's F-Secure, but I need help on getting this fixed one way or another.

I have a program that I want to update, but it has the old task priority object in it, and Fusion tells me I need to install the unicode version and then refuses to load the mfa. But there appears to be no unicode version of the task priority object, so I'm stuck. I would just delete the task priority object, but I can't load the mfa to delete it.

How do I do that?

(I think, someday I might sell an app I built. But so far, the only one using my apps is me. I've created some things I've found useful, both at work and for personal use.)

I'm using the current release, not a beta. I've tried submitting stuff to McAfee before, and it didn't seem to matter. I fixed things for awhile by excluding the file object from McAfee's real time scanner. But now McAfee wants to find all Fusion 2.5 apps to be viruses. Even a BLANK APP that does nothing.

I'm through with McAfee. I officially ditched them today and installed a different antivirus suite offered by my ISP (apparently I was just grandfathered in on the McAfee because I got it when my ISP was offering that).

And it deletes them without notice. It doesn't even bother to quarantine them. You can except out the a particular file in the exceptions from the real-time scanner. But if you change the file, McAfee automatically removes it from the exclusion list. I'm beginning to hate McAfee. I think I'm going to ditch them. But this is an issue that really ought to be fixed.

At first it was just the file object that McAfee hated. But now it doesn't seem to matter. Even a blank exe that does nothing will get scrubbed. If it was made by an earlier version of Fusion, McAfee doesn't seem to have a problem with it. Maybe even an earlier build but I don't know. It seems like anything I've built with 2.5 is now subject to being scrubbed.

With regard to notepad, I meant to say that an independent launch of notepad accomplishes nothing, but launching notepad within Fusion (by launching a designated text file) works, except of course, the text file is open.

Somehow the index program is getting tangled with dosbox from the get go. As long as dosbox is windowed, no problem, but fullscreen causes issues. But if I launch and kill another mmf program, then the problem is solved.

I'm wondering if this has anything to do with the resolution of the index program. It's 1900 x 900. In at least some of the earlier versions, the dosbox crash causes the index program to resize to what may be 640 x 480.

Looks like it is specific to dosbox somehow. With the earlier versions of the index program, even fullscreening an independent dosbox launch while the program is running causes the crash. That is true even if I launch notepad first. But if the program launches notepad from inside then there is no issue (except that notepad is open). With the latest program, I'm launching another mmf program and killing it before dosbox launches, and that works. But I think it was working in one of my versions so long as I do it before dosbox fullscreens. A little more elegant to do it before I launch a dos game at all though.

Refining on my solution: Instead of the one time process of running and killing the dummy file dosprocess.exe being triggered by running a dos program the first time, I have it being triggered on a start of frame condition. This eliminates a visible but brief up and down of the index window. And it ensures that I can jump to other frames without running into the same problem.

Still no ability to automatically minimize the index while the dos game is running and then restore it when the game is done (could minimize but no way to restore---using the wait checkbox brings back the problem). But dosbox would be running on top of the index program, which is good enough.

OK, I have hit on a more elegant solution, though I hope Clickteam can fix this so that the built application behaves the same way as the testing from within Fusion. Here is what I did:

I created a Fusion application that does nothing and titled it "dosprocess.exe". When I click on a "shortcut" in my index program the first time after it is opened, it will start dosprocess.exe, minimize and hide the index program, and then start dosbox and whatever game the shortcut instructs dosbox to start. Then, with the assistance of the "get and kill process" object and a string object, the program detects whether dosprocess.exe is running and immediately kills it. Once dosprocess.exe is killed, the tray object instructs the index program to restore and show. I use global variables to help mediate this process and so it only happens the first time a dos program is run from the index program. This solves the fullscreen issue. Oddly enough, the process only has to be run once for the program not to have fullscreen problems.

I might want to have the ability to minimize the index program while a dos program is running, and I can't do that with this fix yet. But, I'm making progress.

The file folder object doesn't seem to have an option that will help. Even if I could run a program with it, I can't see anyway for it to recognize when the program has stopped running. The execute in console object produces even worse results than the other options I have tried so far.

Volnaiskra - The same problem occurs with the file object. As for the process viewer, I can't make heads or tails of it, and the example is not illuminating. The get and kill process extension is understandable. If only dosbox.exe were not invisible to it! But for some reason it is.

Volnaiskra -- Didn't see your last post. I'll try those.

Decal --- Your proposed fix doesn't work. The same behavior occurs. Once dosbox goes fullscreen, the application becomes visible and dosbox terminates.

Volnaiskra --- It's one of the first things I tried. The same behavior occurs when dosbox goes fullscreen. I have tried mix and matching the full screen options and keeping them all blank. None of it helps.

Another thing I have discovered. If I do not minimize my index program, all I need to do is have the execute-an-external-application command run a text file at start up. So long as the text file is open, I can switch to fullscreen in dosbox without any problems. Weird

OK, I've found a workaround, I think. It requires a second Fusion program whose only purpose is to kill the index program, restart the index program, and then kill itself, and it requires the index program to open the killing program and a text file. If I leave the text file open (minimized or behind the index program), I can use the index program to select a dos game and I can fullscreen it without a problem. When I exit the dos game, all I see is the text file. Then I can close text file. When that happens, the killing program will then do it's thing, and the index program will pop back up, having been killed and restarted. Then I can select another dos game, etc. It's not as elegant as I'd like though.