@danjo frame properties:
![]()
@danjo frame properties:
![]()
I know exactly where is is, and what is does... there was talk about why this hasnt been increased - and Yves said, he would probably increase it. my question is, has he forgot - or changed his mind.
it was set as a default a long time ago; nowdays that default could be much higher without any impact.
After my update to 295.10 my fusion stoped showing accented characters in some fonts, I cant figure why this happened.
fonts.png
Is the same text in both strings.
Not sure if anyone else has noticed or reported this, but the selection box in the frame editor shows in an offset of 1 pixel in the X axis and 1 pixel in the Y axis from the selected object.
This may be difficult to see in high resolution projects or from a far zoom level, but in low resolution projects this is very visible. Attached a screenshort of selecting an 8x8 square object.
Selection Box Offset.png
@goldeng I don't have this issue... Are you sure you don't have a shader applied to the layer or something?
@NaitorStudios
No, I never used shader in my projects (as far as I'm aware of anyway). Just simple pixel-art style. I just reinstalled version 293.10 to see how it looks there. This really odd, as there is an offset still but only from the left and top sides of the object. See screenshot (I had to scale it a little more because the max zoom there is 400%).
Selection Box Offset Comparison.png
I forgot to mention that I'm encountering this in the standalone version, and that I'm running it on my new Macbook Air M1 2020 which I just got recently in Parallels Desktop on Windows 11 on ARM. I just checked that on my main Win10 PC and can confirm that it doesn't occur there in either version 293.10 and 294.12b. Not sure what's going on... If anyone has a hint please let me know. Thanks
I stumbled across a small bug by accident and found out why thanks to @NaitorStudios
In the option to load an image into a frame from file using expression, if the hotspot and/or action value is set outside the range of 100000 it will destroy the object. I accidentally placed one extra zero, didn't notice and was puzzled that the object was being destroyed!![]()