CodeLobster IDE

Hello CodeLobster,

First and foremost, thanks for a great product - I love it.

I'm not a fan of tabs, as other people's code depends on their individual tab settings, and so my YAS regards TABS/SPACES.

I'd like to be able to:
1. Replace all tabs with nn spaces
2. Make a [TAB] key stroke== nn spaces




Thanks again.


Cheers,

Fat Lizard

Hi.

Big thanks for your suggestion.
You may use now "Replace with regexps" for such conversion.

Regards,
Codelobster Team.

Thanks CodeLobster,

Must be obvious, but not to me I'm afraid.
If I try to search|replace, using regular expression selected, I can put \t to find, with ' ' (no quotes) to replace.

I have tried a few different variations, and because I have the [TAB] marker visible, I can see the search engine locating each [TAB], but no replacement is occurring.

Can you explain a bit more precisely please,


Thanks

Hi.

\t works ok.
Do you use our latest version 3.2.1.?
Be sure that you have checked "use regular expression" option.

Regards,
Codelobster Team.

Hello again,

It works perfectly -- looking at computers in the early hours of the morning seems to do strange things with my brain processing

Sorry for the inconvenience over this.

I have had a couple of system crashes however, where CodeLobster simply just closes.
One time I had changed the default encoding to UTF_8, clicked 'Apply', and it disappeared.
Another time I had simply clicked 'Tools' on the top menu when it vanished.


One thing I have found, which I think would be nice concerns debugging.

(although again perhaps it's there and I just haven't seen it)
Once a breakpoint is hit, I really only have the option to either step -into, or, step-over, code.
Having stepped over my block of code, it would be nice to be able to then run the application again, under the debugger, until the next breakpoint is hit.

For example: I have a project (such as the one I sent you) which has a large number of files and classes, spread out amongst numerous directories, and I may have breakpoints set at other locations in the project.

After inspecting my code on breakpoint, it would be nice to run the program until the next breakpoint is hit, where ever that may be located in the project.

Borland used to (maybe they still do) have something like this in their early IDE's.

Cheers,

Fat Lizard

Hi.

1) Debugger issue:
You should press F5 simply to continue running under the debugger until next breakpoint is hit.

2) We heard about periodical crashes of Codelobster.
But we need to have step-by-step instructions for repeating it.
We also try to do it ourself and will do it permanently for resolving these problems.
We are very appreciate for any addition info.

Regards,
Codelobster Team.