Beta Test 2.2.2

Outlaw Game Tools
#1

Qs, comments, nitpicks:

* love the fact that cmd-g does a find-next!

* love the option-click to open either internal/external editor

* the CR vs LF issue seems to be still there, although you crossed it out as a done thing - did I miss any config option maybe ?

* opening a file with the internal editor in a new window makes that window start initially too high on my Mac - part of the top window-bar is moved under the screen’s menu-bar - you can still pick the window up and move it, but it’s esthetically not pleasing :wink:

* I’m intrigued by the snippets feature… but how do they work? how do I paste a snippet in the code while expanding the ^filename?

* also what is this Tools/Launch App menu command - maybe a facility to launch shell scripts or is that wishful thinking on my part :wink: ?

Thanks, Frank.
[import]uid: 8093 topic_id: 9203 reply_id: 309203[/import]

#2

Thanks for the feedback, Frank.

I’ll look again at the CR vs LF issue – maybe I only implemented it for tabs or windows, not both? Or I hit Undo one too many times? :slight_smile:

I’ll also look at the window opening code. Source files that have been opened before should reopen at the position where they were closed. And source files that have never been opened should open up at the same position as the last opened window.

See the two videos at this page for info on the Snippets and Tools Launch:
http://coronaprojectmanager.com/learningcenter/

The PDF file on that page also has a section on Snippets.

Jay
[import]uid: 9440 topic_id: 9203 reply_id: 33621[/import]

#3

Just wanted to say I’m really enjoying the code editor in CPM! Definitely the fastest way to develop code for Corona.

Keep up the fantastic work! [import]uid: 33866 topic_id: 9203 reply_id: 33622[/import]

#4

Ok - snippets are a nice addition!

Now about the App Launching… it doesn’t seem to work with shell scripts (?) - or I do not know how to make it work with those - the idea is to provide arguments to the apps - is that possible?

Lastly, and it’s more a feature request that has been mentioned before: could you parse the terminal window output and substitute the error directives with links that would bring up the editor of choice for the file and line-number? That would be truly useful for all of us who spend a lot of time looking at file names and line numbers and then doing all by hand - for you that shouldn’t be more than 5min coding to get that to work :wink:

Thanks for CPM!

Regards, Frank.

[import]uid: 8093 topic_id: 9203 reply_id: 33646[/import]

#5

My plan was not to do any more upgrades until July when I release v3.0 – but I misnumbered 2.2.2 (should have been 2.3) plus there are a couple little things I don’t want to wait to fix.

So, I’m planning on doing a v2.3 upgrade in another week or two. At that point I’ll try and tweak the Tool Launch thing so you can add arguments. I think all I need to do is allow you to type into that Browse field, right? So you could choose Terminal using the button and then type in any needed arguments.

I must have blanked the feature request for parsing the terminal output, because it doesn’t ring even a tiny bell. But that sure would be a handy feature. I’ll kick that around but it might not see the light of day until at least 3.0.

Thanks.

Jay
[import]uid: 9440 topic_id: 9203 reply_id: 33648[/import]

#6

If you could just push those ^fname/^filename equivalents into the environment while you launch those apps, then we can use those to construct anything we want on the command-line.

You actually do not have to provide support for arguments explicitly as long as I can write a shell script that pulls the filename out of an environment variable and construct the command line in the script.

(Not sure how it works now as I’ve tried to launch terminal sessions, but that didn’t work (?).)

As far as the terminal parsing is concerned, I cannot find that feature mentioned in previous requests - I thought it was posted before, but maybe it is new - it would truly be cool though and would make life more pleasant for those of us who run into bugs one in a while… or slightly more often :wink:

-FrankS.
[import]uid: 8093 topic_id: 9203 reply_id: 33649[/import]

#7

The mac download link for 2.2.2 seems to be broken… :frowning: [import]uid: 8782 topic_id: 9203 reply_id: 33725[/import]

#8

Sorry, I switched to make that the release version but forgot to hide that post. Now you can get 2.2.2 from the normal download links on the right side of that page.

Jay
[import]uid: 9440 topic_id: 9203 reply_id: 33747[/import]

#9

Quick request Jay.

Can we get settings for the default text? Specifically, “bold”, “italic” and “underline” like the rest of the text.

Is it possible to add in highlighting the line that the cursor is on, with a color setting to keep it separate from the “highlight” color?

What is the caret color used for?

Thanks

Mike Hovland
Blue Rocket Labs [import]uid: 5317 topic_id: 9203 reply_id: 34387[/import]

#10

Mike,

I’ll look at adding more formatting settings for the default text, but it probably won’t happen until v3 later this summer (but you never know).

Highlighting the current line should be fairly easy, I’ll see if I can get it in one of the next couple updates.

The caret color is… CARET?!

Sheesh, I meant cursor! How did that happen! Argh! Okay, THAT will be fixed in the next version. :slight_smile:

Jay
[import]uid: 9440 topic_id: 9203 reply_id: 34459[/import]

#11

Trying to search (cmd-F) in the terminal window (actually any preview window) seems to cause CPM to bring up a system log crash window…

Seems to work without issues in code-windows, i.e. non-preview.

-Frank. [import]uid: 8093 topic_id: 9203 reply_id: 34596[/import]

#12

Frank, thanks for that. I can’t actually duplicate that but have gotten that crash report from a couple people, so I’ll look into it. The goal is to actually allow the Find to work in Terminal and Preview, so I need to dig into that code, anyway.

My new game Roly-Polies HD is just about to the point where I can pass it off to my kids to start creating levels, so while that’s happening I’ll be turning back to CPM to tweak a few things. Next update is probably just going to be fixes and stabilizing things to kind of gear up for a *major* v3 update this summer.

Jay
[import]uid: 9440 topic_id: 9203 reply_id: 34630[/import]