WC09 final beta 4 bugs

[PugFish]

Spoke too soon

1. Class method names that are the same as built in PHP functions are highlighted as such, and it also breaks the document outline (same problem as with the types as function names)
2. When a document is in HTML highlighter mode but the active outlining language is not HTML (CSS, JS or PHP in the document outline tool window) the bracket matching style uses the HTML one instead of the respective language.
3. Related to the above, in a PHP file with HTML highlighter the && gets marked as a HTML validation warning saying "The ampersand character should be written as &" even though the active highlighter is PHP.
4. Import settings dialog can be resized
5. When resizing the Manage scripts dialog, the Path: text area doesn't resize so when you make it smaller it covers the Edit and Delete buttons
6. I'm not sure if this is a bug or a feature, but when opening the search dialog it automatically fills the text box with the nearest word to your cursor. Most other apps keep your last search so it's more consistent to do this too. I think it should only automatically fill it in for text you've actively highlighted
7. Related to the above, when choosing an old search from the drop down list it replaces it with a blank line so it's gone the next time you go to use it

And a small feature request, an option to show code snippets in the intellisense popups instead of needing another shortcut to trigger the insert code snippet popup

[KasperTSW]

Hi,

> 1. Class method names that are the same as built in PHP functions are highlighted as such, and it also breaks the document outline (same problem as with the types as function names)

You shouldn't use reserved words or function names for your own types - WebCoder doesn't support that, and it probably won't do it anytime soon. Sorry.

> 2. When a document is in HTML highlighter mode but the active outlining language is not HTML (CSS, JS or PHP in the document outline tool window) the bracket matching style uses the HTML one instead of the respective language.

Actually, it will work like that no matter what, since CSS, PHP and so on are child languages of the HTML highlighter. I'm not able to change that at the moment. Individual bracket settings will only be used when you're using that specific language as a highlighter.

> 3. Related to the above, in a PHP file with HTML highlighter the && gets marked as a HTML validation warning saying "The ampersand character should be written as &" even though the active highlighter is PHP.

When validating HTML, WebCoder will try to remove PHP blocks, so unless you're doing something out of the ordinary, this shouldn't happen. Please post a file where you see this happening

> 4. Import settings dialog can be resized

Fixed.

> 5. When resizing the Manage scripts dialog, the Path: text area doesn't resize so when you make it smaller it covers the Edit and Delete buttons

I changed it so it can't be resized anymore

> 6. I'm not sure if this is a bug or a feature, but when opening the search dialog it automatically fills the text box with the nearest word to your cursor. Most other apps keep your last search so it's more consistent to do this too. I think it should only automatically fill it in for text you've actively highlighted

This is a feature. It works like this in lots of other IDE's, e.g. Visual Studio.

> 7. Related to the above, when choosing an old search from the drop down list it replaces it with a blank line so it's gone the next time you go to use it

Should be fixed now

>And a small feature request, an option to show code snippets in the intellisense popups instead of needing another shortcut to trigger the insert code snippet popup

Added to my TODO list for next version.

[terry_b]

> 6. I'm not sure if this is a bug or a feature, but when opening the search dialog it automatically fills the text box with the nearest word to your cursor. Most other apps keep your last search so it's more consistent to do this too. I think it should only automatically fill it in for text you've actively highlighted

This is a feature. It works like this in lots of other IDE's, e.g. Visual Studio.

I agree with PugFish on this. I think that once you do a search or a search and replace, the fields should contain the string that you searched previously or what you highlighted. On the other hand, you could make this behaviour as an option. It also seems that sometimes the history doesn't keep trace of the strings you searched for.

[PugFish]

You shouldn't use reserved words or function names for your own types - WebCoder doesn't support that, and it probably won't do it anytime soon. Sorry.

I'm not sure we're talking about the same thing. Screenshot below shows count() being highlighted even though it's perfectly legal and in fact necessary if you implement the countable interface. I've found an extra step which is causing the document outline issue, there has to be a $this->something in the highlighted method for it to get messed up (methods defined after it show as global functions and the class variable shows as a class function).

php_problems.png (24.99 KiB) Viewed 209 times

When validating HTML, WebCoder will try to remove PHP blocks, so unless you're doing something out of the ordinary, this shouldn't happen.

That explains it, i'm seeing it in files with no closing PHP tag (this is a Zend coding standard). Shown in the screenshot above.

This is a feature. It works like this in lots of other IDE's, e.g. Visual Studio.

You know, i've used VS and Notepad++ for years and i've never noticed that both of them do this too, but all other non-editor apps I've looked at use the last search. I guess it's not as consistent as I thought

[KasperTSW]

Hi Terry,

>I agree with PugFish on this. I think that once you do a search or a search and replace, the fields should contain the string that you searched previously or what you highlighted.

WebCoder will still respect selected text - if you have any, it takes precedence over the current word. Besides, since the word is highlighted in the search dialog, all you have to do is start typing, to overwrite WebCoder's suggestion. I really do believe that this is the optimal way

>On the other hand, you could make this behaviour as an option.

Since this behavior really shouldn't mess things up for anyone, I would like to avoid implementing yet another setting

>It also seems that sometimes the history doesn't keep trace of the strings you searched for.

This could be related to the bug PugFish describes, in which case it has been fixed now

[KasperTSW]

Hi,

>I'm not sure we're talking about the same thing. Screenshot below shows count() being highlighted even though it's perfectly legal and in fact necessary if you implement the countable interface. I've found an extra step which is causing the document outline issue, there has to be a $this->something in the highlighted method for it to get messed up (methods defined after it show as global functions and the class variable shows as a class function).

Okay, I see. Unfortunately, fixing this could resolve in a range of new problems, so for now, I have decided to leave it as it is, since this is a some what rare case. It's not exactly easy to fix, but I do have some ideas, that I will look into for next version. I hope you can live with it until that

>That explains it, i'm seeing it in files with no closing PHP tag (this is a Zend coding standard). Shown in the screenshot above.

Oh you just gotta love PHP standards . I think I have fixed this issue now

>You know, i've used VS and Notepad++ for years and i've never noticed that both of them do this too, but all other non-editor apps I've looked at use the last search. I guess it's not as consistent as I thought

Hehe no I guess not. I really appreciate this small feature my self - I use it all the time