Script Editor -- 'else' Keyword Spacing Issue

Bug Reports Studio Bugs
#21

[quote] STILL AN ISSUE.

:angry: [/quote]

Cool it lol.
There’s a order in which things get done and asking for something in the middle of December isn’t going to help you.
There’s also plenty of alternatives that you could use instead like Sublime Text 3, Notepad++, etc.

#22

[quote] STILL AN ISSUE.

:angry: [/quote]

Cool it lol.
There’s a order in which things get done and asking for something in the middle of December isn’t going to help you.
There’s also plenty of alternatives that you could use instead like Sublime Text 3, Notepad++, etc.[/quote]

  1. This is extremely frustrating to deal with while actually coding.
  2. I don’t want to go through all the trouble of coding through another program
  3. It has been 7 months.
#23

This actually happened to me the other day. I thought I was crazy.

#24

No issue here.

#25

It has been another 7 months and I am still dealing with this! :angry:

#26

It has been another 7 months and I am still dealing with this! :angry:[/quote]
I had this issue once upon a time, but its been gone for me for a long time.

#27
#28

Ok, so, from what I can tell (The video quality makes reading that code really difficult), this is caused by the fact that you have your parenthesis directly next to the ifs and thens in your code. When I put spaces between these, I no longer experience this issue. We’ll take a look, but for now, I’d suggest putting the spaces on the other side of the parenthesis as a temporary solution.

#29

Haha, it’s like forced coding practices or else consequences! I like it.

#30

Well, we don’t enforce coding practices, but we do have keywords. The parenthesis may be making the script editor think there isn’t an if there. If you just type else and then hit enter, it’ll do the same thing.

#31

I think it’s worth noting that this doesn’t happen with elseif.

#32

Another month of this issue :emo-angst:

#33

Why don’t you just write your if statements without parentheses?

#34

Wow! I couldn’t believe you had kept this thread alive for so long so I decided to take out my work laptop and look into the bug.

Essentially the problem is that the AutoComplete code looks for "if ", not “if(”. Pretty easy fix once I found it. I’ll try to get it submitted when I get to work tomorrow morning.

It’s kind of a weird style but because it is syntactically correct Lua I think we should support it.

#35

I could not replicate this issue on a Mac either.

:,/

Sounds like a you

#36

[quote] I could not replicate this issue on a Mac either.

:,/

Sounds like a you [/quote]

This issue has a perfect repro.

Just write your if statements like this:

if( condition )then

#37

huh
I didn’t actually try to replicate it I just never noticed the problem …

I guess I just got in the habit of doing it automatically. Wow now it’s really screwing with me.
I guess ignorance really is a bliss…

#38

I use parenthesis out of habit. I do my other coding in Java and C# and I’m used to that style.