Re: Code-Explorer and CSS

There seems to be something wrong with the tabs.

Go into Program Settings
-> Program Behavior
-> Uncheck smart file switching

Try to CTRL+Tab or SHIFT+CTRL+Tab, the "tab" will change but the file in the "editor window" will not.

Also, if you try to SHIFT+CTRL+TAB with smart file switching checked, it does the same thing.

freeb0rn:

There seems to be something wrong with the tabs.

Go into Program Settings
-> Program Behavior
-> Uncheck smart file switching

Try to CTRL+Tab or SHIFT+CTRL+Tab, the "tab" will change but the file in the "editor window" will not.

Also, if you try to SHIFT+CTRL+TAB with smart file switching checked, it does the same thing.

Nevermind, I tried replicating this and couldn't for some reason (although I did so twice yesterday). I'm not sure what I am missing.

Hi Jan,

Thanks for this release.

Anyway, some problems which I reported for 4.5.2 b2238 are still in:
- Indent/Unident doesn't work for single line without any selection
- Check spelling: The underline disappers when user clicks on underlined word when wrap line is ON

- Check spelling stops working for *.txt files at all in some scenarios, e.g.:
1. PsPad is running
2. Open some *.txt file
3. Enable spell check-underlineing via PsPad toolbar -> works OK.
4. Close the file and open again -> Enable spell check-underlineing via PsPad toolbar -> stops work at all, PsPad needs to be reseted.

Sometimes PsPad crashes when I try to disable/enable spell check again. The produced crash log will be mailed to you.

Edited 1 time(s). Last edit at 2006-10-31 21:19 by tyzio.

For Indent / Unindent in one line use TAB / Shift+Tab (you can use it for selected block too)

I know problem with SpellCheck and Wordwrap, but I have no solution yet.

Thanks for such quick response.

Quote:

For Indent / Unindent in one line use TAB / Shift+Tab (you can use it for selected block too)

Yes, it is solution but you need to go back to the beginning of the current line

Quote:

I know problem with SpellCheck and Wordwrap, but I have no solution yet.

Cool, I'm looking forward for this fix.

One more think: I found that in LOG parser expression the char * doesn't match the space (0x20) char and it should match everything.
I found it because I try to parse the output from my compiler which align right the line numbers (bellow I replace spaces with _ for better view):
Line___67: W Unknown command "putss"
Line__211: W Unknown command "putss"
Line_2189: W Unknown command "putss"

Right now I'm not able to parse all 3 cases, I try:
Line*%L:*
*%L:*
*%L:%E

phoenix:

Hello,

thx for the update - a great editor.

One thing I found out in the codeexplorer. If you write your css-code like this:

#example1,
#example2,
#example3
{
}

the codeexpl. will show you:

- #example3 (...nothing more)

If you write it like this:

#example1, #example2, #example3
{
}

all ID's are visible in the codeexpl.

Bug or Feature?

--
phoenix0107

it's given by desing. Code explorer parse line by line. It doesn't handle all possible variants of code.

pspad:

phoenix:

Hello,

thx for the update - a great editor.

One thing I found out in the codeexplorer. If you write your css-code like this:

#example1,
#example2,
#example3
{
}

the codeexpl. will show you:

- #example3 (...nothing more)

If you write it like this:

#example1, #example2, #example3
{
}

all ID's are visible in the codeexpl.

Bug or Feature?

--
phoenix0107

it's given by desing. Code explorer parse line by line. It doesn't handle all possible variants of code.

okay, thanks for the answer

phoenix0107:

pspad:

phoenix:

Hello,

thx for the update - a great editor.

One thing I found out in the codeexplorer. If you write your css-code like this:

#example1,
#example2,
#example3
{
}

the codeexpl. will show you:

- #example3 (...nothing more)

If you write it like this:

#example1, #example2, #example3
{
}

all ID's are visible in the codeexpl.

Bug or Feature?

--
phoenix0107

it's given by desing. Code explorer parse line by line. It doesn't handle all possible variants of code.

okay, thanks for the answer

Download the latest build, it's already implemented