[EDIT: Now linked to installers for v2.6.0 with even more goodness. Still mostly untested at this point!]
Okay, let’s say these releases are for people who don’t mind a little excitement.
I’ve been using this version for several days but I updated my compiler and sometimes *that* can introduce things (sometimes even fixes for annoyances), so I need to pound on it some more.
But it seems pretty solid.
So if you’re already using CPM and would like to switch to the latest version, here’s the link:
The installers WILL overwrite your current versions of CPM, so you might want to rename them or something just in case you want to revert back.
You *may* lose your editor syntax colors and have to reset those, but I think I have that taken care of.
Main Things I Hope You Will Notice:
Find window should be much better behaved. It shouldn’t open duplicate windows, you should be able to close it with Command/Control-W, etc.
Fixed Code Generator header template stuff that I broke in 2.5.1.
Fixed text parsing so it only outdents if ‘end’ is on a line by itself.
Added Jump To Line # option under the Edit menu (Command-J).
Split autocomplete words into “official” and user-generated.
Ability in Prefs to specify whether to gather user-generated words for autocomplete.
More error-checking in LoadPreview content to help with Win XP errors.
Fixed Code Generator header template stuff that I broke in 2.5.1.
Let me know how things work out for you.
Jay
PS - If you do NOT want to be a guinea pig, skip this and wait a few days – it will appear as an update automatically when I’m satisfied it’s less broken than the last version.
[import]uid: 9440 topic_id: 14271 reply_id: 314271[/import]
Hey, just wanted to mention a new feature for 2.6, it’s the Jump to Line # that David N. suggested.
I just finished adding it and I can’t believe I hadn’t added it before – it’s really handy!
Just hit Command-J and a little bitty window pops up with a text field selected – type in the line number you want to go to and hit Return. Boom! You’re at that line number and the Jump To window goes away.
Works whether you’re using tabs or windows for editing.
Hit Command-J again and it remembers the last line you went to and is pre-populated – so if you’re jumping back and forth from one thing to another it’s Command-J, Return and Boom! You’re there.
If you’re wanting to type in a different line number, no sweat, because the previous choice is already highlighted so just start typing.
I know, I know, it’s a tiny little feature, but it really adds some zip when you’re jumping around a long code file.
When you get it and start using it, remember to thank David when you see him.
Jay
PS - No ETA on v2.6 at this point – there are several little things like this I’d been meaning to add and a few other bugs that need to be squashed, but I hope to have it available within a couple weeks.
[import]uid: 9440 topic_id: 14271 reply_id: 52636[/import]
you fixed Code Generator header template stuff that you broke twice?
hehe never mind looking forward to check the new stuff out.
[import]uid: 70635 topic_id: 14271 reply_id: 53510[/import]
Jay, in the pre-release update you mentioned you fixed the end problem. Try writing this in maually.
local fucntion something()
timer.performWithDelay(200, function() someVar=12; end, 1)
end
Then go back and make the value 10 or add a space. You’ll see it jump the line back a tab to complete the function. It seems like the parser is looking for the word end. If it exists then it jumps the line thinking it’s completing the object.
Also try naming a variable endXXX. For example I drove myself nuts naming something self.endPoint. Everytime I typed end it jumped it…
Hopefully that helps you understand what I’m talking about. Everything else has been solid. I’m not seeing any headers when I create a new file BUT I’m not seeing the broken text either. The CMD+J has been incredible…
