Hi,
As I've been using phpEd, I've noted down some bugs that I think would make it that much easier to use. They're just listed in the order that I discovered them.
Maybe some of you might like to comment on them, but it would be great to see them included in a future build. Hopefully soon?
.
- When hovering over a variable in debugging mode and the variable has an & in it, the & doesn't show, however it does show in the locals window.
- When hovering over $HTTP_POST_FILES[$strFilename]["name"], the tooltip shows it as undefined, but it shows up correctly in the locals window.
- If phpEd is associated with the .php extension and a file is double-clicked, phpEd doesn't open the last workspace and it doesn't re-open the last workspace when you re-open phpED from a shortcut. It would be better if phpEd remembers the last workspace, even between single file opens.
- The colour changer in the syntax colouring settings tab only seems to remember the colours in the immediate drop down colour picker. If you click Other, any colour you pick is forgotten and the last colour in the colour picker is the one that is stored.
- Undone text should be left highlighted like most editors do.
- Both the tooltips when you hover over a variable and the locals tab show superfluous backslashes (\) whenever there is a slash in the value e.g. a windows filename would be displayed as "c:\\path\\to\\file\\filename.txt". This makes the value really difficult to read.
- When you close an editor window, phpEd positions on the window to the left of the one just closed. It used to position on the last viewed window, which is much more useful.
- Composite field names e.g. ${"prefix$strField"} aren't syntax highlighted i.e. the "prefix$strField" doesn't have the $strField bit highlighted as an in-string field name.
- Instead of having to put a file mask in the Find In Files dialog box to specify which files to search, a much easier way would be the other way round i.e. you should only have to put in the types that shouldn't be searched. This would make the mask list a lot smaller. If you don't want to do this, perhaps phpEd should come pre-fill it with the most common masks e.g. *.php,*.htm,*.html,*.inc,*.css,*.js,*.txt,*.ini,*.log,*.tpl,*.htaccess.
- When you hover over an array in debug mode, if the array has a nested array, the tooltip popup outdents the elements of the nested array instead of indenting them.
- If you have 'Line Number in Gutter' on in non-gutter mode, then switch the gutter on and switch it off again, the line numbers are switched off too. This didn't happen before, so please could you make sure that, if line numbers were on before the gutter was switched on, they are left switched on when the gutter is switched off?
- When debugging mode is started, phpEd doesn't become the active window automatically like it used to, except sometimes immediately after it is started. Could phpEd be made to switch to it's own window automatically everytime the debugger is started e.g. by refreshing the browser window?
- If you have a multi-line if, e.g.
if ($strMsgType <> "Error"
and funNotNull($pstOfferId)
):
|
the active line of the debugger positions on the second line, instead of the first line. which also means that any breakpoints set on the first line are ignored. Perhaps it would be better to have the debugger position on the first line of the if instead.
- far too many backslashes are being displayed in the immediate tab:
when I display the following variable:
It shows:
: string = "The affiliate referral cookie expiry period\\n(<span class=\\\"link-norm\\\"><a href=\\\"javascript:funMakePopup(\\'\" . PAGE_SHOW_HELP . \"?Show=gnudate\\\\',\\\\'help\\\\',\\\\'\" . POPUP_PARMS_WIDE . \"\\')\\\">(in Relative GNU Date format)</a></span>)."
|
whereas the real value from the database is:
The affiliate referral cookie expiry period\n(<span class=\"link-norm\"><a href=\"javascript:funMakePopup(\'" . PAGE_SHOW_HELP . "?Show=gnudate\\',\\'help\\',\\'" . POPUP_PARMS_WIDE . "\')\">(in Relative GNU Date format)</a></span>).
|
This makes things very confusing, as I don't know for sure how many slashes have ended up in the variable, so it makes it very difficult to debug the variable in say something like an eval statement, which is notoriously difficult to try to get working at the best of times. It would be nice if the values of variables in the immediate window could show the actual value with no extra characters inserted.
- The split screens should be totally independent of each other, other than the fact that they display the same page e.g. there should be no re-positioning of both of them to the same place in the file when you save or switch word wrap on on one of the screens and if you highlight something in one screen the highlight should not show in the other screen as well.
- Currently, if you switch on word wrap on one tab, every tab has it switched on, which is very frustrating. It would be good if there was a separate word wrap setting for each tab, so that you can have it switched on in some tabs and off in others.
- The Extended Select option highlights doesn't distinguish between special characters at the end of words e.g. with the string "height=400");, when you drag your selection over the last quote, phpEd automatically includes all the 3 characters "); instead of each character, one at a time. This is very annoying, because you have to manually backspace the ) and ; out of the highlighting (which are very rarely required to be included in the selection), before you can continue. A much more useful behaviour would be to highlight each special character separately, when they occur grouped together like in the example.
Having said that, I can see that there could be situations where highlighting all the special characters would be desirable, so alternatively you could use the behaviour that Word uses, which makes highlighting words in different ways, a real breeze. What Word does is to highlight the whole set of special chars first then, while still holding the mouse button down, allows you to backtrack to the start of the special chars, so they are unhighlighted, then track forward again, highlighting the special chars one at a time. This way, you have the best of both worlds.