Printable View
As a system extension waiting for input I am not surprised there are interferences with controls.Quote:
Originally Posted by PixelABCD
Have you tried the data grid action : window -> Disable ? That should prevent the data grid from catching any input from controls while allowing access to datas.
@Brovic. I didn't know. So I tried this as the start of frame action: Window > Disable. This does not fix the control x issue, ControlX doesn't read input, so still no change. Anyway, I will use a hardcoded event and some actives strings as a list instead, it will be a bit more complicated than using a data grid but this way I have no extension conflict.
@CT Looking forward new F2.5 update, looking like one big and promising so far. Pity F3 is so far away, also hoping we could see more about it this year.
McAfee will falsely detect and delete the following files.
Module name: Suspect!71c2d9cd6c1c
ProgramFiles(x86)>ClickteamFusionDeveloper2.5>Exte nsions>Unicode>kcfile.mfx
ProgramFiles(x86)>ClickteamFusionDeveloper2.5>Data >Runtime>Unicode/sdrt.exe
For now building with "Unpacked EXE" enabled avoids this problem. Could you report it?
Attachment 31304
I found an error. Sometimes when copying a global object to another frame, the object does not result identical, despite having the same name, etc..
In the example I posted I modified the drawing of one of the objects and as you can see the other one didn't change.
Found an old bug that went unnoticed for long...
Objects with Static 'movement' will trigger Collide conditions every time they move despite never stopping overlapping the obstacle (backdrop or active).
Oddly enough if the obstacle is an Active with any movement but stopped, it also works correctly... So seems like having anything other than Static changes the Collide behavior, but Static makes Collide not work correctly.
Another small mistake:
When in the Base Frame of a Global Events, I update the icon of a particular object, the object's image doesn't get updated in the Global Events itself.
Bug.
I don't remember this happening before, but maybe it always did. When you reactivate an event inside a deactivated group, the event will run. Even though it's sitting inside a deactivated group (and nothing inside a deactivated group should run, right?). In the example below, you can see that the object gets scaled up to 4
https://bit.ly/3JOzgfU
@Volnaiskra I've seen something similar, rarely happens if you undo after disabling a group and deleting/adding some events, but in my tests, whenever I got this, trying to do something to this event or group would crash Fusion.
I think it's because the groups is put into comments, like in real code, so it's like there is no group here. Only way to deactivate a group once for all is to set it to "deactivate" in code or at start.Quote:
Originally Posted by Volnaiskra
Oh, this shouldn't be possible, I mean, you can activate a event inside a inactive group, this is wrong.
But yeah, it comments the event line, not the entire group, meaning active event lines inside a inactive group will work, it doesn't seem like something we should be able to do tho.
I've seen this cause a crash when happening after a undo/redo, so it might be a problem...