Button, Active System Objects, and Active Objects (as buttons) Not Working

After purchasing the HTML5 exporter, I am finding that I cannot get any of my applications to work properly due to problems with making buttons with objects that are supposedly supported and should be working properly. I sent a bug report with an example illustrating each of these problems in Sept but so far nothing has happened. This is very frustrating since they are objects that are essential to just about any project. I think that these problems should be either fixed quickly or acknowledged so I can ask for my money back. I'm probably overreacting and I hope I am just plain wrong in some way about the problems. I would like to be proven wrong - but please do so. Thanks. I love Clickteam products but have not been impressed with the exporters to date.
Steve

Issue #3816 has been reported by drnebula drnebula.
________________________________________
Bug/Issue Reports #3816: Problems With Active System Boxes
• Author: drnebula drnebula
• Status: New Report
• Priority: Normal Priority (5)
• Assignee: Yves Lamoureux
• Category: HTML5 Object
• Target version:
• Core product(s): Fusion 2.5
I created a html5 test app for buttons and active system objects. The app is at:
www.darngoodsolutions.com/html5/index.html
The file is attached.
The buttons work fine whether clicked with the mouse or on a touch screen. The active system boxes work fine as buttons when clicked with a mouse but not at all on a touch screen. And the system boxes don't work being enabled and disabled either with a mouse click or on a touch screen.
Hope this helps.
Steve
html5_testA.mfa
Files html5_testA.mfa (88.3 KB)

Ah I missed this report for some reason, too many emails at the same time probably, I'll take a look.

Actually I remember this report. I fixed the enable/disable issue for the ASB object in the build 287, but forgot to update this report.

I was unable to fix the problems with ASB on a touch screen at that moment and got disturbed by other things, and then I forgot about it. Too many things to do...

PS: afaik the touch screen issue only happens on PC desktops, not on Android or iOS devices, correct?

Yves,

I rebuilt the test app using the latest version of MMF 2.5 Dev (v287.9) and retested it. I tested it using: 1) a PC running Win 7 and using IE 11, 2) a laptop running Win 10 and MS Edge, and 3) a Samsung Android tablet. In all cases: the buttons work fine with a mouse or by touch as before, the active system boxes now work with a mouse or by touch. They also seemed to enable and disable.

The one thing that did not work with either a mouse or by touch on any platform, was increasing and decreasing a counter by clicking on an active system object. This did work when run from inside MMF 2.5.

Thanks for looking into this. We are making progress. I will rebuild some of my applications and see if they also are working better.

The new sample can be found at:
www.darngoodsolutions.com/html/html5/index.html

Steve

Yves,

More, I hope, interesting information. I rebuilt several applications and started testing them on my PC running Win 7.

1) I found that one of the buttons was not showing the button text and also was not being disabled. This button showed the new icon for a button (Fusion 2.5) while the other buttons showed the old icon (Fusion 2.0). See attached pic.

2) On the active system boxes that I was using to move the counter. They are working but the system box is displaced in both directions from where it "should" be. So if you click in the location it should be, the counter is moved. But if you click on the system box image, it does not work. See two other attached pics.

Hope this helps. Any solutions to this would be helpful. I will continue testing on Win 10 and Android.

The HTML5 app can be found at:
http://www.darngoodsolutions.com/htm...Gas/index.html

SteveAttachment 21927Attachment 21928Attachment 21929

>> the active system boxes now work with a mouse or by touch.

It's a bit more complicated than that. Touches on ASB work fine with Edge and IE 11 on desktops but not with Chrome / Firefox (though double-touch works on Firefox).

I've checked the problem that you get with "increasing and decreasing a counter by clicking on an active system object". This is a display issue that was fixed in the build 287 too:

Quote:

---

- System Box objects: in undetermined cases the hot spot of the image could be different from 0, causing the image to be displayed at a wrong location. To fix it, re-edit the image in the build 287.3 or greater (= open the picture editor) so that the hot spot is forced to 0,0.

---

This issue doesn't appear in some runtimes as they ignore the hotspot. But the HTML5 runtime uses display routines that always take it into account. To fix it edit the image of these ASB objects and click OK to validate it (with the build 287.9 or above).

So the problem that remains is the issue with touch monitors on desktop machines with Chrome and Firefox.

Great. I'll check that out.

There is also the button issue noted above. I tried to go back and change the "old" buttons to "new" buttons, but then all of the new buttons did not show text or disable.

Thanks,
Steve

The suggestion to edit the images of the ASB objects solved the problem. Fantastic.

As far as the old and new button issue. I tried to replace the old buttons with new ones - the same problem persisted even when there was one old button in one frame and only one new button in another frame. I finally deleted all of the frames except one and when I deleted the one old button and added one new button, it finally worked. Not too great of a solution to replace a huge number of buttons.

I also tried making a screen capture of the button and pasting it into an active object. But in HTML5 the text sizes change, so it did not look very good.

I'm running out of ideas on this one.

Steve

I've rebuilt another app into HTML5. This one runs fine EXCEPT that the buttons do not show that they are disabled. They are disabled, and work properly, they just don't show that they are.
See:
http://www.darngoodsolutions.com/htm...ons/index.html

The Stop button placed at the top of the main screen as a test is not shown as disabled. When Start is clicked, most of the other buttons should be disabled.

Steve

Another ported HTML5 app with same problem - buttons not showing being disabled.

www.darngoodsolutions.com/html/AtNum/index.html

Steve

Could you post a very simple MFA with a single button that has this issue in the bugbox please?

Here is an example from a scaled down version of one of the apps that is not working properly. The left button in frame 1 does not show the text. In frame 2, when the 2nd button from the left is clicked, other buttons should be disabled (greyed out). They are not.
SteveAttachment 21931

See: http://www.darngoodsolutions.com/htm...em3/index.html

Thank you for your help so far. As far as the buttons not disabled (not greyed out), perhaps that was a bad example. How about a better one. After starting from the opening page, the Play Again button should be greyed out. When the Start Game button is clicked, the Start Game and Directions buttons should be greyed out.
Steve
See: http://www.darngoodsolutions.com/htm...But/index.html
Attachment 21935

I'm having problems with ASB used as buttons. They work fine when run in MMF but do not show the text when ported to HTML5. I searched the posts but could not find anything that answered this problem.
Steve