Bindows 4.7 - Release Notes
Support for Microsoft Edge
We have developed a key bundle feature. It is
similar to a string bundle, but where a string bundle contains strings selected
by user language, the key bundle contains BiKeyStroke objects selected by
User definable key bundles
As a developer you can decide to replace the entire key bundle or override
specific shortcuts. Add the <KeyBundle/> tag to the <Resources> </Resources> section.
See the sample KeyBundleTest.xml for example use
Built-in overrides for Mac clients.
The default keybundle includes a set of keystrokes that are used only on a
Mac. These override the PC keystrokes automatically.
You can also add your own shortcuts. BiKeyboardEvent and BiMouseEvent
include two new methods matchesBundleShortcut(sName) (keyboard events only)
The output from BiKeystroke.toString() is different on a Mac than on a PC. It
displays the modifier symbols that a Mac user expects. Both formats work as
input when parsing a shortcut string (disregarding platform).
Bindows includes a new panel component that animates by between open and
closed states. It can be configured in a number of ways and can hold any Bindows
components. It can be docked to any side inside any Bindows component and also
operates as an inline component.
See the samples CollapsiblePanelTest and CollapsiblePanelTest2 in the
applauncher for example use
We added a class which adds a third state to BiCheckBox. The check-box may display a third "undetermined" state.
This is useful e.g. when handling a single property for
multiple objects at the same time.
For example use, see the ThreeStateCheckBoxTest in the applauncher
New grid/tree IP column type
We made a new grid and /or tree IP' column type available.
New date validation
We have added an optional basic date validation for the datetimepicker. When it is used, if a user fills a date picker with an invalid date (for example 32.01.12, 29.02.12)
an error dialog occurs.
The message for the error dialog can be set manually.
This version adds support for the latest versions of all major browsers, including Internet Explorer 11, Microsoft Edge, Firefox 41, Safari, and Chrome 45.
In response to customer requests, we added several minor improvements
See the changelog for details.
This release contains several bug fixes. See the changelog for details.
Known Bugs and Issues
- Drag-n-drop is not working when continuous selection is used. This
is used by default for OLAP grids and if you need to be able to drag a
cell in an OLAP grid you should turn off
its selection model.
- Right to left is not working correctly for BiTree, BiGrid, BiTreeView
- Multiple smaller issues with Right To Left (RTL) exists.
loses selection when update is called.
with icons might return wrong preferred size before icons are loaded.
To make sure this does not lead to trouble set the image size for the
icons or preload the images.
- Non pixel border widths results in incorrect behavior. Please only
use pixel border widths for best result.
puts first focus on the Next/Previous buttons even though there are
text-fields etc on the selected page.
- When putting a BiIframe
in a BiWindow
the focus-root is not honored.
- There is no way to refer event target within an action in
- Nested async calls make events bubble
- Menus: No support for multiple frames. The menus will open in the frame where the Bindows script file (application.js or bilauncher.js) was added.
- Jaws articulates the word "blank" before the selected value of some components e.g.
- The selected item in BiComboBox,
does not receive focus and is not followed by magnifiers.
- In Bindows, the standard key combination Shift+Ctrl+F6 is used
to navigate out of a child window and out of an iframe. This has a
meaning in Window-Eyes so an alternative key combination needs to be
- Slider: Holding arrow key buffers a lot of keypress events
without refreshing the view.
- Splash Screen: Jaws sometimes reads splash screen contents
- Jaws 7.10 reads the entire text content of a focused
- Iframes: It is sometimes possible to tab through the links in
an iframe and when reaching the end end up anywhere in Bindows.
- Iframes: Certain versions of Jaws and Window-Eyes do not
articulate the iframe element title but the content document title,
which cannot (must not) be altered by Bindows.
- Sometimes descriptions are articulated twice or more.
- Ctrl+Tab does not trigger a keydown or keypress event in IE7
if the browser tabs are displayed. The keydown event is used in
Bindows to switch between child windows and between tab pages.
Switching between tab pages can still be done by focusing the tab list
and using the arrow keys. However, there is no built-in alternative for
switching between sub windows in Bindows. The recommendation if you
want this functionality is to launch your application using biExec
which opens a new window without tabs and therefore with the events
active. This also applies to FireFox
- The method getDescription for iframes may not work depending
on which screen reader is used. A workaround is available in the
accessibility developers guide.
- When leaving a sub menu the screen reader should say leaving
sub menu instead of just "leaving menu".
- Focus outline is sometimes not visible for some components and
also depends on how you focus them; tab or shift-tab.
- A text field that is blurred sometimes still shows the caret and
the selection color is still using the Highlight color which makes it
look like it is still focused.
- Move and resize handles do not work when used to move the
- The gauge label is not always centered correctly. Consider using the much more
advanced BiGauge2 instead.
- Don't use https:// with PNG images. We use a plugin
(AlphaImageLoader) to display PNG images (as IE doesn't handle
transparency correctly without it). For the image to be displayed it needs to be
cached, and SSL content is, by default, not cached. It may be possible to
turn on caching for the image, in which case it should work.
Internet Explorer 8
- Problems starting applications in Protected Mode (Windows Vista Business)
In Windows Vista - Business Edition, Internet Explorer 8 has the option of turning on/off the "Protected Mode" for the various zones.
We have received reports that turning off the "Protected Mode" causes an error when trying to open a new window. This is a problem when using BiLauncher which requires the permission to launch a new window.
The workaround for this problem is to turn on the "Protected Mode" option. This is the value by default and is recommended to leave the option enabled.
In Windows XP there are no reports of errors. The "Protected Mode" option is not available in Windows XP since all zones have "Protected Mode" enabled.
Internet Explorer 9
- Icons in trees/grids are not centered correctly
Internet Explorer 10
- 'Auto clean' button can not be disabled for input fields.
- Ellipsis for overflowing text will not appear in mozilla based browsers.
- Labels with text align center and icon position set to top or
bottom are a bit jumpy, i.e. the icon move around depending on the
keyCode is sometimes incorrect in a keypress event (for special keys).
The reason for this bug is that Internet Explorer and Mozilla are
handling keyboard events differently.
- Focus and blur events are inconsistent when using BiRichEdit.
- Right to left does not work for BiToolBar.
- Avoid using -moz-appearance when creating custom themes.
Sometimes setting a border cannot override the border set by the
appearance property. The workaround is to change the theme to not use
- SVG charts does not support gradient color fillings on sections
(columns, bars etc...) .
- In Firefox versions prior to 3.6, a component with overflow=auto that is moved relative to it's
parent component causes rendering issues in the area that is outside the parent component,
sometimes leaving artifacts on screen.
- ToolBar doesn't show uncomplete buttons in WebKit
- Bindows focusing system is not supported on Safari 3.2.1 and older.
No known issues
- Apple's Aqua theme (used on Safari Mac/PC and Firefox Mac) requires a certain minimum size of an element (e.g. a BiList or BiTextArea) for the native scrollbars to render properly.
If the contents inside an element require scrollbars and the element's size is below a certain size, then the scrollbars will not function properly and will just look like a gray bar.
To work around this you can increase the height or minimum height on your component to accommodate for the native scrollbars (e.g. around 70 pixels for a BiList).