Formatted TextControl 3.2.1 - FTParagraph.Alignment_Type

I have an app with FTC 3.2.1 that works.
When I try to recompile the project, I get an error related to FTParagraph.Alignment_Type. “Alginment_Type” is an enum.

However, I don’t understand the cause of the error or how to fix it. Can anyone give me some advice?

1 Like

Same problem here - workaround: using Xojo 2025R1.1

Looks like something changed in Xojo between R1.1 and R2.1 which broke this part…

Could be related to this RN from 2025r2:

Structures with invalid fields no longer causes the compiler to crash or trigger an assertion. We now raise a compile error and highlight the problematic structure field. (78844)

If a field of type ENUM in a structure is invalid, then I will probably have to revise the FTC for this structure.

That doesn’t sound too good at first.
I’ll have to take a closer look at that.

Is “Size ?” really legal for a Structure that’s supposed to be well defined?

I don’t think so. I’m just wondering about this error in the structure.
I just want to use the FTC and not change it if possible. I guess I have no choice but to adjust it.

I can’t find a difference.

Unfortunately, as BKS parted ways I no longer have access to a FTC license (and I believe someone else owns it now). I’m afraid I can’t help in any other ways at this point. My suspicion is that structure is indeed wrong, but you’ll need a reference for what it’s supposed to look like to fix it.

Perhaps you need to get in touch with the new owner of FTC?

I think Xojo have introduced a compiler bug when using an Enum in a structure. It appears to be related to the structure specifying Enum as Module.Enum.

The sample project I have attached compiles with Xojo 2017r3 but does not compile with Xojo 2025r2.1. I don’t get the same error as you so there might be more than one bug.

Xojo Enum In Struct Bug.xojo_binary_project.zip (3.8 KB)

2 Likes

Logged as:

xojoinc/xojo#79918

Blerp, I apparently forgot it was open sourced :sweat_smile:
I think there’s a bigger issue at hand though, found thanks to people more smart than me!

I got the information this has been fixed for the next Xojo version.

2 Likes