Earlier this year

• Jun 20, 2009

  issue 19 (Mouse wheel doesn't work over code listing) reported by p.pawliczuk   -   What steps will reproduce the problem? 1. point mouse over listing 2. scroll the wheel What is the expected output? What do you see instead? I expect to scroll code with wheel. Now it isn't possible. What version of the product are you using? On what operating system? XDC 1.0b5, WXP SP2

  What steps will reproduce the problem? 1. point mouse over listing 2. scroll the wheel What is the expected output? What do you see instead? I expect to scroll code with wheel. Now it isn't possible. What version of the product are you using? On what operating system? XDC 1.0b5, WXP SP2
• Jun 20, 2009

  issue 18 (Variables tree) commented on by p.pawliczuk   -   Oh, I meant superglobals and already traced variables.

  Oh, I meant superglobals and already traced variables.
• Jun 08, 2009

  issue 18 (Variables tree) commented on by an...@webkr.de   -   A few lines above it says: ----- xdebug.dump.* Type: string, Default value: Empty * = COOKIE, FILES, GET, POST, REQUEST, SERVER, SESSION. These seven settings control which data from the superglobals is shown when an error situation occurs. ----- As you can see, GLOBALS is not included. When I add a watch panel, I actually can add a watch for those seven superglobals, if that is of any use for you. But to save traffic you can also add them one by one. Run a search for "property_get" in the dump and you can also see that GLOBALS is not retrieved. You can ask Derick on the xdebug mailing list whether there are any reasons against providing GLOBALS... possibly the circular references pose a problem.

  A few lines above it says: ----- xdebug.dump.* Type: string, Default value: Empty * = COOKIE, FILES, GET, POST, REQUEST, SERVER, SESSION. These seven settings control which data from the superglobals is shown when an error situation occurs. ----- As you can see, GLOBALS is not included. When I add a watch panel, I actually can add a watch for those seven superglobals, if that is of any use for you. But to save traffic you can also add them one by one. Run a search for "property_get" in the dump and you can also see that GLOBALS is not retrieved. You can ask Derick on the xdebug mailing list whether there are any reasons against providing GLOBALS... possibly the circular references pose a problem.
• Jun 08, 2009

  issue 18 (Variables tree) commented on by p.pawliczuk   -   I'm almost sure it's possible: http://www.xdebug.org/docs/stack_trace "xdebug.dump_globals Type: boolean, Default value: 1 Controls whether the values of the superglobals as defined by the xdebug.dump.* settings whould be shown or not." I've tried to enable/disable - eg. SERVER have been dumped into inspect in both cases. Dump you asked: http://www.nopaste.pl/d23

  I'm almost sure it's possible: http://www.xdebug.org/docs/stack_trace "xdebug.dump_globals Type: boolean, Default value: 1 Controls whether the values of the superglobals as defined by the xdebug.dump.* settings whould be shown or not." I've tried to enable/disable - eg. SERVER have been dumped into inspect in both cases. Dump you asked: http://www.nopaste.pl/d23
• Jun 08, 2009

  issue 18 (Variables tree) changed by an...@webkr.de   -   Oh, ok. Are you sure that the Variable list is retrieved from xdebug and not just derived from code analysis? Could you provide me with a log of the xdebug communications when variables are retrieved from xdebug? You can enable it in php.ini with: xdebug.remote_log=/tmp/remote_log

  Status: New

  Labels: Type-Enhancement −Type-Defect

  Oh, ok. Are you sure that the Variable list is retrieved from xdebug and not just derived from code analysis? Could you provide me with a log of the xdebug communications when variables are retrieved from xdebug? You can enable it in php.ini with: xdebug.remote_log=/tmp/remote_log

  Status: New

  Labels: Type-Enhancement −Type-Defect
• Jun 07, 2009

  issue 18 (Variables tree) commented on by p.pawliczuk   -   There must be a solution. Look at PHPed screenshot: http://www.php-debugger.com/dbg/ gifs/phped32.png - part "globals" or PHP Eclipse - http://devzone.zend.com/images/ articles/2930/eclipse_debug.jpg - right side of window.

  There must be a solution. Look at PHPed screenshot: http://www.php-debugger.com/dbg/ gifs/phped32.png - part "globals" or PHP Eclipse - http://devzone.zend.com/images/ articles/2930/eclipse_debug.jpg - right side of window.
• Jun 06, 2009

  issue 16 (Close in inspect doesn't work) Status changed by an...@webkr.de   -  

  Status: Accepted

  Status: Accepted
• Jun 06, 2009

  issue 17 (Two issues at about box) Status changed by an...@webkr.de   -  

  Status: Accepted

  Status: Accepted
• Jun 06, 2009

  issue 18 (Variables tree) Status changed by an...@webkr.de   -   What do you mean? Some kind of automatically populated watch window that shows all variables in the current scope? I'm afraid that's not possible, because I have to request them by name and I cannot request $GLOBALS.

  Status: WontFix

  What do you mean? Some kind of automatically populated watch window that shows all variables in the current scope? I'm afraid that's not possible, because I have to request them by name and I cannot request $GLOBALS.

  Status: WontFix
• Jun 06, 2009

  issue 18 (Variables tree) reported by p.pawliczuk   -   In many PHP frameworks and larger scripts, there is a stack trace of all variables used in scripts. I think that variables tree next to the code with them would be a great feature. Now, it's necessary to point each variable by cursor and then use inspect. Using variables tree would much improve readability and user experience. ;)

  In many PHP frameworks and larger scripts, there is a stack trace of all variables used in scripts. I think that variables tree next to the code with them would be a great feature. Now, it's necessary to point each variable by cursor and then use inspect. Using variables tree would much improve readability and user experience. ;)
• Jun 06, 2009

  issue 17 (Two issues at about box) reported by p.pawliczuk   -   What steps will reproduce the problem? 1. click on links or 2. look at the version number What is the expected output? What do you see instead? I expect correct version number (I was really confused if I had executed correct version after update). Links don't work too. What version of the product are you using? On what operating system? XDC 1.0 b5, WXP SP2

  What steps will reproduce the problem? 1. click on links or 2. look at the version number What is the expected output? What do you see instead? I expect correct version number (I was really confused if I had executed correct version after update). Links don't work too. What version of the product are you using? On what operating system? XDC 1.0 b5, WXP SP2
• Jun 06, 2009

  issue 16 (Close in inspect doesn't work) reported by p.pawliczuk   -   What steps will reproduce the problem? 1. start debugging 2. use inspect window 3. click "close" at bottom of window What is the expected output? What do you see instead? Window should be closed. ;] What version of the product are you using? On what operating system? XDC 1.0 b5, WXP SP2

  What steps will reproduce the problem? 1. start debugging 2. use inspect window 3. click "close" at bottom of window What is the expected output? What do you see instead? Window should be closed. ;] What version of the product are you using? On what operating system? XDC 1.0 b5, WXP SP2
• Apr 26, 2009

  xdc-1.0b5.zip (xdc 1.0 beta 5) file uploaded by an...@webkr.de   -  

  Labels: Featured

  Labels: Featured
• Apr 23, 2009

  issue 15 (Update property windows in realtime (watch)) reported by an...@webkr.de   -   Open property windows should be reloaded after every run period to reflect the current state.

  Open property windows should be reloaded after every run period to reflect the current state.
• Apr 23, 2009

  r24 (* Settings.settings: New AppSetting break_on_script_start * ...) committed by an...@webkr.de   -   * Settings.settings: New AppSetting break_on_script_start * SourceFileForm.cs: Breakpoints can be toggled using the F9 key * SourceFileForm.cs: Property are displayed in tooltip * MainForm.cs: Optionally debugging can be started automatically on script load

  * Settings.settings: New AppSetting break_on_script_start * SourceFileForm.cs: Breakpoints can be toggled using the F9 key * SourceFileForm.cs: Property are displayed in tooltip * MainForm.cs: Optionally debugging can be started automatically on script load
• Apr 23, 2009

  issue 14 (Open files manually or break on new file) reported by an...@webkr.de   -   It should be possible to open files from the server by manually giving the file path on the server. Alternatively or additionally break on every new file to have xdc load that file.

  It should be possible to open files from the server by manually giving the file path on the server. Alternatively or additionally break on every new file to have xdc load that file.
• Apr 23, 2009

  issue 13 (Auto break-on-script-start) reported by an...@webkr.de   -   It should be possible to break on script start only if there are no breakpoints in no files. This shoould be the default.

  It should be possible to break on script start only if there are no breakpoints in no files. This shoould be the default.
• Apr 23, 2009

  issue 6 (Better variables inspection) commented on by an...@webkr.de   -   Part 1 is implemented

  Part 1 is implemented
• Apr 23, 2009

  issue 12 (Clear breakpoints when file is closed) commented on by an...@webkr.de   -   Should they really be cleared?

  Should they really be cleared?
• Apr 23, 2009

  issue 12 (Clear breakpoints when file is closed) reported by an...@webkr.de   -   When a file is edited on the server, one has to close the file to have it reloaded. When doing so, breakpoint should be cleared because they are probably in different lines now.

  When a file is edited on the server, one has to close the file to have it reloaded. When doing so, breakpoint should be cleared because they are probably in different lines now.
• Apr 23, 2009

  r23 (* Settings.settings: New AppSetting listening_port * ConfigF...) committed by an...@webkr.de   -   * Settings.settings: New AppSetting listening_port * ConfigForm.cs: Close button now works ;) * MainForm.cs: Listening port is now configurable

  * Settings.settings: New AppSetting listening_port * ConfigForm.cs: Close button now works ;) * MainForm.cs: Listening port is now configurable
• Apr 23, 2009

  issue 11 (Port configuration + Proxy support) reported by an...@webkr.de   -   Port configuration + Proxy support

  Port configuration + Proxy support
• Apr 23, 2009

  issue 8 (client freezes) Status changed by an...@webkr.de   -   Maybe I will asynchronous net I/O later. At the moment I don't think it's worth the effort.

  Status: Deferred

  Maybe I will asynchronous net I/O later. At the moment I don't think it's worth the effort.

  Status: Deferred
• Apr 23, 2009

  issue 4 (Automatically start debugging with a breakpoint on the first...) commented on by an...@webkr.de   -   I think it DOES break at the first line, doesn't it?

  I think it DOES break at the first line, doesn't it?
• Apr 23, 2009

  issue 7 (Debug starts on wrong line) Status changed by an...@webkr.de   -   It breaks at the first break point or notice, if configured to do so.

  Status: Invalid

  It breaks at the first break point or notice, if configured to do so.

  Status: Invalid
• Apr 23, 2009

  issue 9 (Invalid length for a Base-64 char array) Status changed by an...@webkr.de   -   If this happens when a source file is empty, it is fixed. If this happens during debugging, please provide sample code or request debug build.

  Status: Invalid

  If this happens when a source file is empty, it is fixed. If this happens during debugging, please provide sample code or request debug build.

  Status: Invalid
• Apr 23, 2009

  issue 6 (Better variables inspection) Status changed by an...@webkr.de   -  

  Status: Started

  Status: Started
• Apr 23, 2009

  issue 5 (Debugger breaks out for reasons unknown) Status changed by an...@webkr.de   -   This was probably the issue with automatic breaking on notices. Fixed.

  Status: Fixed

  This was probably the issue with automatic breaking on notices. Fixed.

  Status: Fixed
• Apr 23, 2009

  issue 2 (Unhandled exception clicking on debug -> run) changed by an...@webkr.de   -   Cannot reproduce

  Summary: Unhandled exception clicking on debug -> run

  Status: Invalid

  Cannot reproduce

  Summary: Unhandled exception clicking on debug -> run

  Status: Invalid
• Apr 23, 2009

  issue 8 (client freezes) changed by an...@webkr.de   -   I don't think it's worth the effort to receive messages asynchronously. I could employ a timeout.

  Status: WontFix

  Labels: Priority-Low −Priority-Medium

  I don't think it's worth the effort to receive messages asynchronously. I could employ a timeout.

  Status: WontFix

  Labels: Priority-Low −Priority-Medium
• Apr 22, 2009

  xdc-1.0b4.zip (xdc 1.0 beta 4) file uploaded by an...@webkr.de   -  

  Labels: Featured Type-Archive OpSys-Windows

  Labels: Featured Type-Archive OpSys-Windows
• Apr 22, 2009

  r22 (Tagged 1.0 beta 4) committed by an...@webkr.de   -   Tagged 1.0 beta 4

  Tagged 1.0 beta 4
• Apr 22, 2009

  r21 (* PropertyForm.Designer.cs, DebugNode.cs: Added ellipsis but...) committed by an...@webkr.de   -   * PropertyForm.Designer.cs, DebugNode.cs: Added ellipsis button for long strings * SourceFileForm.cs: It's no longer necessary to select an identifier to inspect its value, simple right-click is enough * Status log is top-down instead of bottom-up * MainForm.cs: Debugging will automatically restart and listen after script finished * MainForm.cs, MainForm.Designer.cs: Added Options menu item * Resources.resx: Images for ellipsis button * Settings.settings, app.config: Added some Application Settings * Client.cs: Request breakpoint on notice only when configured to do so * Aga.Controls.dll, WeifenLuo.WinFormsUI.Docking.dll, ICSharpCode.TextEditor.dll: Added dependencies * Aga.Controls.dll: Updated to 1.6.1.0 * ConfigForm.cs: New form for configurations * PropertyDetailsForm.cs: New form for long strings * NodeEllipsisButton.cs: New node control for TreeViewAdv that shows an ellipsis button and opens a PropertyDetailsFrom with its value when clicked

  * PropertyForm.Designer.cs, DebugNode.cs: Added ellipsis button for long strings * SourceFileForm.cs: It's no longer necessary to select an identifier to inspect its value, simple right-click is enough * Status log is top-down instead of bottom-up * MainForm.cs: Debugging will automatically restart and listen after script finished * MainForm.cs, MainForm.Designer.cs: Added Options menu item * Resources.resx: Images for ellipsis button * Settings.settings, app.config: Added some Application Settings * Client.cs: Request breakpoint on notice only when configured to do so * Aga.Controls.dll, WeifenLuo.WinFormsUI.Docking.dll, ICSharpCode.TextEditor.dll: Added dependencies * Aga.Controls.dll: Updated to 1.6.1.0 * ConfigForm.cs: New form for configurations * PropertyDetailsForm.cs: New form for long strings * NodeEllipsisButton.cs: New node control for TreeViewAdv that shows an ellipsis button and opens a PropertyDetailsFrom with its value when clicked