Back to Release Notes

Contents 1 New Features 1.1 System Discoverability and Usability 2  Bug Fixes 3 Known Issues

[edit] New Features

• Debugging Breakpoints: You can now set a breakpoint in your code and view the state of the current variables and objects in scope. Often, we release features that I like to refer to as “deposits” on big, multi part features. Debugging is obviously a large feature of Bungee Connect and we will continue to add to the functionality we’re releasing today. For now, the feature set is small, but incrementally very valuable to users of the system. Give it a shot, let us know what you think and help guide our future development on this feature.
  http://docs.bungeeconnect.com/wiki/index.php/How_To_:_Using_Debugging
• Event Viewer Re-Design: The event viewer is continuing its facelift. Events are better organized with improved filtering capabilities. Better details of events. Iconized labeling of events.
  http://docs.bungeeconnect.com/wiki/index.php/How_To_:_Setting_up_Logging
• Chooser Filtering: The chooser is much smarter now about showing only context appropriate items. This has been a major issue for a lot of new developers who aren’t as familiar with the system. The chooser should be much simpler and won’t let you do things that “don’t make sense” anymore.
  http://docs.bungeeconnect.com/wiki/index.php/How_To_:_Using_the_Chooser
• Property Editor Filtering: Just like the chooser, the properties pane has been revamped to hide certain property settings that “didn’t make sense” and allowed developers to do things that clearly wouldn’t work
• Promotion of Nested WSDL Typelibs: In the case that an imported WSDL file has a nested typelib, Bungee will now handle those differently on import. The nested typelib will be promoted to the top level with the rest of the imported typelibs. The WSDL will still function as expected.
  http://docs.bungeeconnect.com/wiki/index.php/How_To_:_Importing_a_WSDL_File

[edit] System Discoverability and Usability

Ongoing Control Polishing: We’re continuing our control polishing, you’ll notice some new example code that can be imported on the start page that shows, in great detail, how some of our controls work and how they fit in the Bungee model. These code pieces and their accompanying documentation are a great place to start your exploration of Bungee. We will continue this effort over the next several months and you will be seeing more and more example code pieces for, not only controls, but also Bungee Design Patterns on the start page. The list of controls we have on the start page is very dynamic. We add and adjust the list regularly so check it often. We currently have the following on the start page:

• MultiColumnList: http://docs.bungeeconnect.com/wiki/index.php/Control_:_MultiColumnList
• TextEdit: http://docs.bungeeconnect.com/wiki/index.php/Control_:_TextEdit
• Label: http://docs.bungeeconnect.com/wiki/index.php/Control_:_Label
• Button: http://docs.bungeeconnect.com/wiki/index.php/Control_:_Button
• DynamicForm: http://docs.bungeeconnect.com/wiki/index.php/Control_:_DynamicForm

[edit]  Bug Fixes

• As always we fix a large number of bugs in each release. Some of the more visible fixes include:
• Google Map Control has had a significant bug fix pass. Too many to mention here, but you should notice an improvement with how that control works
• Dragging a case statement into another case statement caused the statement to lose code
• Statistics and Stats working more consistently in the Preferences tab
• The Default property now applies correctly to Image Buttons
• Enter Key now properly firing default button on Safari
• MD5 hash repaired in the Bungee API
• After withdrawing from a design group the withdraw button was remaining enabled.
• Login page re-branded

[edit] Known Issues

• Each time we release a new version of the Builder (not necessarily each time we roll out new code) you’ll see that your “recent solutions” section of the start page is wiped out. It still works, and will start building up again, but the fact that it clears out is an unintended side effect that we’re working to fix.
• Re-opening an open solution doesn’t really open it. If you’re working in a solution and think to yourself: “Hey, I want to lose all my changes cause I don’t want to keep them, so I’m just going to re-open this solution.” That won’t work. In order to do what you want in this case (lose all changes on purpose) then you’ll need to fully logout and log back in and re-open your solution to make that work.
• Updating a deployment is still rough. At this point, if you want to update a Deployment to point to a new Post, after making the change, you’ll need to trigger the update to take effect by simply changing the text field of the application URL by: copying the current text of the url, make a change to it and press enter, then paste back in the original url and press enter, then click the Update button.