| Bug ID # |
Description |
Reported Against |
Status |
Workaround |
| 1 |
Breakpoints set on a 'for' loop statement will only break the first time encountered. |
1.0 Beta 1 |
Fixed
1.0 Beta 2 |
Set the breakpoint on the first line inside the for loop block. |
| 2 |
Breakpoints set on CLINIT statements, in the constructor, and in the install() or register() methods are ignored. |
1.0 Beta 1 |
Fixed
1.0 Beta 2 |
Setting a breakpoint at the first line of the process() method will allow you to view the results of these functions. |
| 3 |
When clicking on an editor window that is out of focus, the text caret changes position. |
1.0 Beta 1
1.0 Beta 2 |
Fixed
1.0 |
Click on the title bar of the editor window before clicking on the text inside. |
| 4 |
The amount of free RAM for the emulated iButton is only an approximation. |
1.0 Beta 1
1.0 Beta 2
1.0 |
In Progress |
None. |
| 5 |
Using the keyword search in the online help causes numerous exceptions to be thrown. |
1.0 Beta 1
1.0 Beta 2 |
Fixed
1.0 |
None. |
| 6 |
The convenience method booleanArrayFromByteArray() has an incorrect line:
if(inArray[start + i] == true) |
1.0 Beta 1 |
Fixed
1.0 Beta 2 |
Replace the line with:
if(inArray[start + i] == (byte)1) |
| 7 |
Set a breakpoint, run in debugger. Then clear all breakpoints and run in debugger again. The debugger stops on the breakpoint that was cleared. |
1.0 Beta 1 |
Fixed
1.0 Beta 2 |
Clear all breakpoints isn't currently clearing in the debugger. Setting new breakpoints works correctly, so either set a breakpoint on a line that won't get called often, or exit and restart the program. |
| 8 |
Call 'setOutgoingLength' with a value greater than the actual length of the byte array that is sent with 'sendBytesLong'. The byte array sent when running in debugger will be the length that was set with 'setOutgoingLength' (instead of the length of the byte array actually sent.) The array is padded with zeros. |
1.0 Beta 1 |
Fixed
1.0 Beta 2 |
Use the convenience function 'sendByteArray', or make sure to call 'setOutgoingLength' with the correct size. |
| 9 |
Record text macros sometimes ignores case in recording keystrokes. |
1.0 Beta 1
1.0 Beta 2
1.0 |
In Progress |
Re-record the macro. |
| 10 |
When calling the sendByteArray method several times in a single run, an APDUException could be thrown. |
1.0 Beta 1
1.0 Beta 2 |
Fixed
1.0 |
Remove the line:
apdu.setOutgoingLength((short)data.length);
from the sendByteArray method.
Add the line:
apdu.setOutgoingLength(MAX_SEND_LENGTH);
in the process() method after the call to apdu.setOutgoing().
(Where MAX_SEND_LENGTH is at least the size of the largest array to be sent in that run.) |
| 11 |
Hitting the 'Refresh' button in the APDUSender window to update the installed applets window throws an exception with version 1.0 iButtons. |
1.0 Beta 1
1.0 Beta 2 |
Fixed
1.0 |
None. |
| 12 |
Infinite loops in the iButtonInserted or iButtonRemoved functions of host code running in debugger caused the IDE to lock up. |
1.0 Beta 1
1.0 Beta 2 |
Fixed
1.0 |
None. |
| 13 |
Make fails when multiple host files exist in the project and only one of the source files was out of date. (Same problem with applet files.) |
1.0 Beta 1
1.0 Beta 2 |
Fixed
1.0 |
Choose Rebuild all instead of make. |
| 14 |
Functions that rely on 'arraycopynonatomic' in applet files cause the debugger to throw a EmptyStackException. |
1.0 Beta 1
1.0 Beta 2 |
Fixed
1.0 |
None. |
| 15 |
The transaction buffer functions are not implemented in the iButton simulator. |
1.0 Beta 1
1.0 Beta 2
1.0 |
In Progress |
None. |
| 16 |
Port handle occasionally not released after running in debugger. (iButtonAdapterInUse exceptions get thrown.) |
1.0 Beta 1
1.0 Beta 2
1.0 |
In Progress |
Restart iB-IDE. |
| 17 |
Options that contain a space in the misc. switches textfield on the Compile Options dialog don't get tokenized and used correctly. |
1.0 Beta 1
1.0 Beta 2 |
Fixed
1.0 |
None. |
| 18 |
iButton applets that throw exceptions other than the ISOException class do not compile correctly using JDK 1.2. |
1.0 Beta 1
1.0 Beta 2 |
Fixed
1.0 |
None. |
| 19 |
Typing Alt-f while an editor has focus brings up the File menu AND adds 'f' to the current editor. (Same problem with all Alt-key combos.) |
1.0 Beta 1
1.0 Beta 2 |
Fixed
1.0 |
None. |
| 20 |
Modal dialogs in host code can cause the IDE to lock up when running in debugger. |
1.0 Beta 1
1.0 Beta 2 |
In Progress |
Set the modal parameter to the constructor of the dialog to false while you are debugging. |
| 21 |
Closing the project while running in debugger puts the IDE in a "locked" state. |
1.0 Beta 1
1.0 Beta 2 |
Fixed
1.0 |
Stop debugging before closing the project. |
| 22 |
Set a breakpoint, then run in debugger using APDUSender and send the correct process to hit that breakpoint. Then add a new breakpoint on the next source line and hit continue. The new breakpoint will not be hit until you stop debugging and run in debugger again. |
1.0 Beta 1
1.0 Beta 2 |
Fixed
1.0 |
None. |
| 23 |
Use the GotoLine Dialog or the Find Text Dialog. The correct line is displayed and highlighted. Clicking in the window will now scroll you to the beginning of the document instead of leaving the cursor on the highlighted line. |
1.0 |
Fixed
1.01 |
None. |
| 24 |
Sha1MessageDigest generateDigest() throws an uncaught exception in the iButton simulator. |
1.0 Beta 1
1.0 Beta 2
1.0 |
Fixed
1.01 |
None. |
| 25 |
Selecting a different port under the Ports menu occasionally fails. |
1.0 |
In Progress |
Choose the new port and restart iB-IDE. |
| 26 |
Windows created by host programs are not closed when stop is chosen from the iB-IDE menu. |
1.0 |
Fixed
1.01 |
None. |
| 27 |
Choosing to run with a project containing only an iButton applet disabled the stop option. |
1.0 |
Fixed
1.01 |
Restart iB-IDE. |
