Scite...

[Squat]

...has gone to shite? It no longer gives me any color-coding hints and bolding. It's making bug-hunting next to impossible.



Also, there's something much worse that makes it so I simply can't use this new script editor even for one more second. It's autofilling in my words without even prompting me, so I'm ending up with "Vectorector" and "Stringing" every time and it's driving my up the freaking wall. I simply can't undo more than 20 years of typing and I never use auto-finish words because I can practically type the word as fast as the dumb machine can replace it and display it anyway. I certainly don't like to have to stop-stutter every 2 seconds while writing in anticipation that the stupid computer's gonna think it's smart all of the sudden and start doing a lot of crap I didn't tell it to and start tossing all over my flow.

If I open the old Scite it seems to work fine and I'm happy.

So, is there any way to point the new release to open the old Scite editor or to replace the new Scite outright? I don't want to break my install yet so I'd rather ask, but I want to go back to the old one....or get a new script editor. I already scoured the options and tried to fix the new one...been at it all morning. I'm kinda done with it and I really enjoy the last one so there's only the issue of me having to now hand-open every script file with it. I need it integrated back in and I'm hoping the GC editor is merely pointing to the scite.exe that I can replace.

[Ron]

I prefer the older SCI editor myself too. On the top bar, you can select Language and set it to GameCore Script which will get you the different text colors back, but it still tries to autocomplete too much (there is probably a way of setting that too).

I did the alternative, re-associating the .gsl, .lay and .sty extensions with the older version though Windows Explorer (see below)




*** You will have to use trial and error between the two SCI's to find the right one. Also, but sure to check the "Always use..." box.



From here, it should open the older version directly from GC

[LutinMalefique]

I agree, the new Scite is a nightmare. 

[Squat]

Thanks Ron I'm gonna try that

[pixel_legolas]

You can also browse for the previous version as you have installed it in another folder

[DPF]

I noticed a funny thing when going through the GC RC1 tutorial on mini-map where you need to un-comment a line ,
and I was suprised to see that Ctrl-Q will not UN comment, it just adds another set of //~.

Didn't realize the version was different. Thanks..

A little off topic, I'm happy with RC1 so far. Loaded up one of my BV projects and instead of failing to run or load, it makes the error log for reference, but still loads up to editor, and will run game anyway, so converting and debugging old projects for GC is looking relativly painless atm.

[Tiles]

So there is really no way to turn off the nightmare feature? Five seconds and i am ready to throw Scite out of the window. Nobody can work with that autocomplete feature on.

EDIT, i knew there was a solution. Click at Options/Open Global Options File. This opens the SciTEGlobal.properties file. Scroll down to Line 249. And comment it out by placing an # in front of it.

From:

249 autocompleteword.automatic=1
250 autocomplete.choose.single=1

To:

249 #autocompleteword.automatic=1
250 #autocomplete.choose.single=1

And voila, no autocomplete anymore

Hmm, would be nice when this would be a menu option though.

Okay, now let's find out why SciTE always forgets the Language settings. Becomes cumbersome when you always need to change it first.

[LutinMalefique]

thanks for the tips Tiles.

[Tiles]

You're welcome

Hmm, that language thingie seems to be a bug. ScitTE manual states that the language in use is determined by the extension. Seems that *.gsl is not defined as GameCore Script yet.

[Squat]

WTF! I can manually open the Scite from RC2.1, but I cannot choose it as a default program to open the .gsl files with. That's the first app in my entire life that's refused to register that. Whenever I browse XP to choose that .exe for it, it just returns to the list and tries to default to internet explorer. So when I hit "Edit Script" I see the main bar for GC flash and then nothing happens.

EDIT: Nevermind I reinstalled 2.1 after removing everything. I remember reading instructions saying it's ok to install over the top of RC2 and when I did that, it had them both in there. Didn't realize was doubled over on itself. I wouldn't suggest anybody installing any full app over another in any case, unless it's a true upgrade. Besides, RC2 and RC2.1 didn't even install as the same thing.

My suggestion is to back up the projects directory and uninstall each new version. That practice always seems to get me at a clean start.

[gekido]

strange - the copy of scite is identical from what i'm aware of - it's always been a bit foggy how to get all of the syntax highlighting and so on to work properly with it, but i'm not sure how things got messaged up.  basically in the globaloptions config it specifies which languages to load - all i did was map the gsl extension to the c/c++ properties options so that it would / should highlight the same.

will look into it and see if there's a quick fix that i can post up.   and yes i do agree that the autocomplete option is very annoying for anyone that types more than a word a minute - i have it disabled as well.

i'd like to get an API document written up for scite sometime in the near future as well - this will provide proper autocomplete of functions, allow inline documentation (of a sort) and so on.  unfortunately the old one that we had got very out of date so i chose to not include it with the build.

either way, thanx for pointing this out - i'll add it to my list of things to get polished up for the version 2.0 release.

on a semi-related note:  does anyone have another open source prefered editor that they would us rather include?  i've bene using programmers notepad alot lately as a scite alternative - but it has even less documentation than scite with regards to how to setup custom syntax highlighting / mapping to languages, so i haven't included it with the release. 

note: the editor must be open source of some kind (ideally with a bsd license) so that we can properly bundle it with the engine.

[Squat]

I'm actually fine with Scite to be honest. It's not missing anything. It fails to color some words, but I think we can fix that ourselves. I whined at first, but the languages setting fixed my problems.

My suggestion is to actually separate Scite from the GC bundle so that we don't update it anymore. That, or provide an option in the install to choose to install it or not.

Let us get used to this one or find our own script editors. Since it's text, I wouldn't put this as something an engine developer really needs to worry about being responsible for. It's fantastic that you're concerned about easing our burdens, but you merely need to let us know what's best to use, and offer at least one on your scite.

In the end, it wasn't working because I had two installs of it, one within the other's folder. Reinstalling brought it back to perfect and autocomplete was easy to shut off. Open global properties and search "auto" and comment out the two lines.

If somebody finds a sweeter editor than Scite, I wouldn't suggest removing scite and putting that in and having it install each time. I'd probably get pissed if I had to learn a new one when I get used to this. I know I can choose to use it instead, but why install a new one? I'd just put a hardlink somewhere for the developers to get it ourselves and put a direct download to the scite editor.

[Ron]

I like Scite too. I haven't tried any other editors, so I really have nothing to compare it to though. One of my favorite things with it is I can 'undo' until the cows come home  and it keeps each file undo seperate from each other.

[gekido]

Yeah I could definitely set it up as a seperate component for the installation - that wouldn't be too hard.

[Spaz]

Wow, I just found this thread.   What a blessing to be able to turn of that stupid autocomplete!  That is the most useless function in the world!  Thanks, Ron!  And I agree, it should be a menu option.