Back to Sequence Viewer

Changes in previous versions

November 26, 2017

Changes in Sequence Viewer 6.2a

Solved bugs

• File > Export: If 'Event variables' was selected, the 'Export' button remained disabled.
• Text > Auto assign keys: the 'Assign' button remained disabled after a string was found.
• Keys > Find keys and Text > Find text: if text and codes of a sequence were not linked, checking or unchecking did not work correctly.
• A number of minor flaws in the user interface are solved.

Improvements

• Keys > Find keys: (un)marking sequences and (un)checking events can now be undone.

August 11, 2017

Changes in Sequence Viewer 6.2

The most important change is that part of the code is rewritten in a lower level language. This greatly improved the speed in a number of (tedious) procedures:

• Edit > Waveform: Calculating the waveform (about 5 times as fast).
• Edit > Waveform: Calculating the loudness, silence and pitch of waveforms (up to 10 times as fast).
• Codes > Define agreement: Calculating the agreement and the alignment between sequences (about 50 times as fast).
• Codes > Assign agreement (up to 25 times as fast.
• Codes > Agreement matrix, cluster sequences: Calculating the agreement matrix (up to 20 times as fast)
• Text > Find text, Auto assign keys, Auto code: Finding texts with a resemblance less than 1 (up to 100 times as fast).

As a consequence version 6.2 only runs on Intel based macs.

Solved bugs

• A number of actions in the main sequence window were not autorecorded with autorecording on: go to a particular sequence number, selecting an event variable, add a new sequence and (un)check events.
• File > Export: Tabs remained invisible if "event text" was selected for export with the textbox show tabs and returns checked.
• Text > Find text, Auto assign keys: If text was found and the "Edit sequence" window was open, the found text became deselected.
• A number of minor flaws in the user interface are solved.

New features and improvements

• A button is added to the main sequence window in order to switch between playing the audio or videofile, and make a selection of the event text when clicking at an event text with linked texts and codes. This is useful if you want to add a key or change the text style of a particular piece of text when an audio or video file is open.
• File > Export: A number of export optionsin case of export for statistical programs are added, in particular re exporting texts. Moreover, this procedure is added to the Command Editor
• Event variables > Convert to code variable is completely redesigned. First to make it more simple and intuitive and second, to be able to add the procedure to the Command Editor.
• Codes > Convert codes to event variable: the same as above.

May 1, 2017

Changes in Sequence Viewer 6.1d

Solved bugs

• Text > Auto code : "Replace all" caused an endless loop.

March 27, 2017

Changes in Sequence Viewer 6.1c

Solved bugs

• Edit > Waveform: The progress bar when assigning sound characteristics to event variables didn‘t work correctly.
• Text > Text count: The "Count" button should be disabled if no event variable is entered.
• Text > Word frequencies: The output showed the table twice. Part of the description of the setup appeared at the wrong place.
• Text > Word frequencies: In case "code variable", "event variable" or "sequence variable" is selected as "by variable", the "Count" button should become disabled until a (legal) variable name is entered.
• Sequences > Check data: Checking the overlap of keys in case of exclusive keywords was incorrect.
• File > Export: The "Keep open " button was not appropriately initialized.
• Text > Auto assign keys: "Replace all" could enter into an infinite loop if the word that was found was at the end of the event text.
• Edit > Assign empty codes: Solved a bug in creating the output.
• Keys > Find keys, Delete keys, etc.: When typing a keyword, and the name of the key was automatically completed, the execution button ( "Delete", "Find", etc.) nevertheless remained disabled.

New features and improvements

• A small progress bar (below the execution button) was added to Sequences > Check data, Text > Find text, Text > Auto code, and Text > Auto assign keys, replacing the common progress bar. The advantage is that the common progress bar could partially hide the main sequence window, e.g. when a particular text was found.
• Added to the Command Editor: Text > Auto assign keys and Text > Auto code.

January 5, 2017

Changes in Sequence Viewer 6.1b

Solved bugs

• When a Sequence Viewer file version 3.0 is read, the information (properties) re sequence variable SEQSIZE was not correctly converted.
• The calculation of DT average was incorrect.
• Clearing the sequence text in ‘Clear sequences’ did not remove text keys and word links.
• ‘Find text’ did not work correctly with both resemblance < 1 and "match where at end".
• If text was found with the ‘Find text’ or ‘Auto code’ setup window, the found text sometimes did not correspond with the selected text in case this text occurred more than once in the event text.
• ‘Replace all’ in the ‘Find text’ setup window sometimes replaced the wrong texts.
• If text was found using the ‘Find text’ setup window, the found text was deselected in case the ‘Edit sequence’ window was open.
• When both ‘Replace if last code of event is typed’ and ‘Move to next event after replace’ in the ‘Edit sequence’ window where checked, the next event code was not selected after typing the last code.
• ‘Auto fill’ of the ‘Edit sequence’ window produced incorrect event codes in case the event texts contained empty lines.
• ‘Split link’ in the ‘Edit sequence’ window, sometimes split the event text at the wrong word.
• The ‘Learn’ button in the ‘Edit sequence’ window didn’t work.
• An empty event text in the ‘Suggest codes’ window was not correctly stored.
• Changing the suggested event code in the ‘Suggest codes’ window did not enable the ‘Store’ button.
• Solved a problem with editing values of sequence variables in the sequence variables drawer, or values of event variables in the main sequence window (in the ‘codes and event variables’ mode).
• When the name of a sequence variable in the sequence variable drawer was clicked to change it’s value, the present value was not shown.
• Moving the key field slider of the text or time keys window when renaming a key, could change the length of that key.

New features and improvements

• The 'Clear Sequences' setup window is extended with ‘Clear marks’ and ‘Set sequence variables to ‘M’’.
• Setting the start and end point when creating a new key is improved.
• When changes in the data are undone, the sequence variables drawer and the information fields drawer now remain open (if already open).

July 18, 2016

Changes in Sequence Viewer 6.1a

Solved bugs

• Calculating te pitch (in the 'Waveform' window) could freeze Sequence Viewer. This usually only occurred with audio files with a low sample rate and 8 bits sample format.
• When the 'Waveform' window was opened the info erroneously suggested that the resample rate was 10 percent. Actually the resample rate was higher if the sample rate of the audio file was lower than 22050.
• In case of a long continuous pitch graph (that is, a graph without gaps), the graph was only partially displayed.

New features

• If you move the mouse over the name of the event variable that is selected with the popup menu in the main sequence window (below 'Show event variable'), the label of this event variable is shown in the help field of the toolbox.

June 28, 2016

Changes in Sequence Viewer 6.1

Solved bugs

• In some cases the state of buttons or menu items (enabled or disabled) did not correspond to what you should expect. For example:
- The toolbar buttons to insert symbols may be disabled whereas they should be enabled or vice versa.
- The edit men items for ‘Undo’, ‘Copy’, ‘Cut’, ‘Copy’ and ‘Paste’ may be disabled whereas they should be enabled or vice versa, or didn’t give the expected result when enabled.
- If text was found and selected with ‘Find text’, the ‘Text style’ end ‘text keys’ popup menus of the tool bar remained disabled.

• A number of problems with word links are solved. Most notably:
- Entering a space in a word of a word link (thus creating two words), or adding a word before or after a word of a word link, caused that the word link pointed to two words at the same time. Now the word link points to the second word.
- If a sequence had a large number of word links, clicking on a word link sometimes selected the wrong word link (thus providing wrong information, or deleting the wrong word link).
• A number of problems with text selection are solved (e.g. loosing the selection after 'Find text').
• In the 'Find text' setup window, when replacing text, the replace button should become disabled if you selected text different from the found text.
• In the 'Find text' setup window, after replacing text with the option key down (to stay with the same sequence), the replace button remained enabled, but should become disabled
• Removing a key using the text keys popup menu of the toolbar sometimes didn’t remove that key.
• Adding a key using the text keys popup menu of the toolbar sometimes sometimes scrolled the event text field through and back.
• When a sequence had only one key, removing this key was sometimes not possible.
• Undoing a newly added key in the time keys or text keys window, did not work correctly.
• Flagging the selected text key in the main sequence window when adding a new key, or editing existing keys was not always consistent.
• The help button of ‘Define keys’ did not open the correct help page.
• The help button of ‘Pattern options’ did not open the correct help page
• The Help button of window ‘Count sequences’ did not work..
• The 'Assign' button of 'Txt > Auto assign keys' showed the wrong help text in the toolbox.
• After marking sequences with “Find sequences”, the message box showed “events found” instead of “sequences found”.
• The 'Convert keys' setup window (Keys menu) sometimes showed the wrong layout.
• In the ‘Convert event codes to keys’ setup window, you couldn’t edit the keyword
• In ‘Import file with codes’, if both the ‘separate codes by a space’ and the ‘extend codes’ checkboxes were checked, the ‘shortest code’ showed a 0 (should be 1), whereas the sequences were extended with a ‘-‘.
• In ‘Import file with codes’, when ‘Truncate codes’ and/or ‘Extend codes were checked, these ceckboxes became disabled and could not be unchecked again.
• When you imported a file with codes to create a new Sequence Viewer file, and the number of code variables was larger than 1, Define Sequences did not work correctly.
• If the number of code variables was 1, Mask events in Define Sequences didn’t work correctly.
• In the 'Define sequence variables' window, you could obtain an error message in the help field of the toolbar that a variable name was illegal whereas actually there was nothing wrong with the name.
• The vertical scrollbar of the values and value labels field in 'Define sequence variables', did not work correctly (in OS X 6 or older).
• The up an down arrow buttons in 'Rearrange event variables' did not work correctly in some cases (e.g. if there was no event time).
• Mark sequences up and down (Sequences menu) didn’t work.
• The output of 'Word frequencies' (Text menu) sometimes displayed strange characters.
• Resizing the Waveform window sometimes changed the size of the Settings drawer.
• Repeating a t-test using the 'Previous setup' button, only remembered the dependent variable.
• In 'Check data' (Sequences menu), when an error was found re an event variable, sometimes the wrong sequence was shown.
• Clicking on the event text to play the corresponding sound file, didn’t work when the sequence was locked.
• When you opened an audio or video file, clicked on an event text to play the sound or video, and clicked once again to stopit, and then closed the audio or video file, you could no longer make a selection of the event text.
• In the print tab of the Sequence Viewer Preferences, if ‘Add page numbers’ was unchecked, the slider for the header margin should become disabled, whereas the slider for the top margin should become independent of the setting of the slider for the header margin.
• In the ‘Frequencies of events’ setup window, if you selected an event variable, and clicked the same variable once again, the name of a sequence variable appeared.
• Changes made to sequence variable ‘STARTTIME’ and event variables ‘Onset time’ and ‘Offset time’, were not considered as (minor or major) changes to the file. Thus, when closing the file, you were not warned that you made these changes.
• Changes made to the event text were not always considered as changes; when closing the file, you were not warned about these changes to the event texts.
• Entering a return in the file info text of the file settings, could corrupt the file.
• Checking or unchecking an event code using the “edit sequence” window, did not update open setup windows re the number of checks.
• Changing the cost in the ‘Define agreement’ setup window, did not recalculate the agreement.
• In some cases, when a setup window became inactive (e.g. because you clicked on something outside this window), and active again (because you clicked in the window again), wrong fields could become focused, causing misleading texts in the setup window.
• When a ‘View event codes’ picture was sent to the output, a wrong heading was shown, whereas information about using a sequence definition and selected sequences were incorrect (actually, a ‘code time view’ always concerns only one sequence).
• In the auto Assign keys setup window you should obtain an error message if you used wildcards with a resemblance less than 1.00.
• In the ‘Correlation matrix’ setup window, if you clicked at the row or column variables field, the thumb of the scrollbar did not correspond with the scroll of the field with the list of variables.
• If a word is selected in the sequence tex, and thus the text keys button in the toolbox is enabled (if you have text keys), and you click a window of a different program, and then goes back to Sequence Viewer, the text keys button becomes disabled, also if the text remains selected.
• If sequence text was copied and pasted into MS Word, the pasted text could contain tags re text keys and word links, unknown to Word. Now these tags are removed when you copy sequence text.

New features and improvements

• You can now send a waveform to the clipboard or save it as a file on disk..
• Creating and editing word links is changed and (hopefully) improved; see the help file for details.
• 'File export' has more options, whereas the user interface is made more straightforward.
• A number of improvements in the user interface, most notably with respect to the selection of event codes.

August 19, 2014

Changes in Sequence Viewer 6.0d

Solved bugs

• If (part of) value labels were changed only with respect to their case (upper to lower case or vice versa), the 'change' button remained disabled ('Define sequence varibles', 'Define event varibales' and 'Define codes' windows).
• The output of 'Compute event variable' did not show if a sequence definition was used.
• If you find an event code with 'Codes' > 'Find event codes', and the 'Edit sequence' window is open, the found event code should be put into the edit field of the 'Edit sequence' window. This was not the case however, if the view mode is 'codes and event variables' or 'codes only'.
• After clicking 'Find' in the 'Find value of sequence variable' setup window, the 'Find' button changes into 'Find next'. If you next click the (un)marked sequences selection icon (at the bottom of the setup window), this change did not have effect. For example, if you changed the icon from unmarked sequences to marked sequences, the program keeps searching the unmarked sequences too. The same bug appeared in the other find windows (event variables, codes and text).
• In rare cases, using the 'Restore' button in the 'Edit sequence' window, sequences were only partially restored (e.g. causing values of sequence variables to disappear).

New features

• In the 'code and event variables' view mode (of the main sequence window), value labels of event variables are shown if you move the mouse over a value with the shift key down.
• In the 'Edit sequence' window, you can now move the selected event upwards or downwards.

July 1, 2014

Changes in Sequence Viewer 6.0c

Solved bugs

• The 'Show labels' checkbox in the Sequence variables drawer didn't work correctly.
• If 'Include event codes' in the 'Import (code and) event variables' setup window is not checked, one event code (with all dashes) is added (which is correct), but the number of code variables remained 0.
• In the 'Rearrange event variables', the first two event variables are disabled in case the file has no event times (if the file has event times the first two event variables are the onset and offset time, and should be disabled).
• After using the 'Select all' button in the 'Add sequence variables' setup window (File > Import), it was not possible to remove one of these variables from the list.
• When adding value labels to sequence or event variables (in the 'Define sequence variables' and 'Define event variables' setup windows) the scrollbar was not updated, making it sometimes impossible to scroll to a particular value.
• Clicking in the last column of the 'codes and event variables' field of the main sequence window (the last event variable), sometimes (un)checked the event instead of selecting the clicked value.
• When you didn't change the text 'Enter event text here' in the 'Add events' setup window (Sequences menu), this text was entered as italic grey text in the sequence text field (instead of plain black text).
• In the 'Find event codes' setup window, when 'Replace all' was used, event codes were not replaced if the new event code was equal (neglecting case) to the old event code, and no question marks were used.
• In the 'Find event codes' setup window, when 'Replace' was used, you could obtain an unjustified error message that no event code was selected.
• A number of minor (innocent) bugs were solved.

New features

• A new import facility was added to the import options, allowing you to add event variables to an existing file.

May 15, 2014

Changes in Sequence Viewer 6.0b

Solved bugs

• Marking and unmarking sequences using 'Find text' (un)marked the wrong sequences.
• A number of problems are solved with applying sequence definitions.
• When the 'Waveform' window is opened, in some cases the 'Assign event times' tab is selected, but the content of the 'Loudness analysis' tab is shown.'

April 17, 2014

Changes in Sequence Viewer 6.0a

Solved bugs

• New users were not able to continue after personalizing the program.

February 25, 2014

Changes in Sequence Viewer 6.0

Sequence Viewer 6 has a number of new features, as well as many improvements in the user interface. The file structure is changed to account for the new word link feature and text options. Files created by Sequence Viewer 6 cannot be read by Sequence Viewer 5.x and earlier. Files created by older versions can be read by Sequence Viewer 6, and saved in the new format.

Due to the numerous changes, script files created by the Command Editor using version 5 of Sequence Viewer will likely encounter errors. If you load an old script file in the Command Editior however, the script is automatically adjusted. If you next save the script file, you can again use the script to run scripts automatically.

New features

Waveforms

You can now perform waveform analyses of linked audio files (of type AIF). Waveforms can be used as an alternative method for entering onset and offset times. Probably more important, waveforms can also be used to calculate speech characteristics, like pitch, or silences. Speech characteristics can be (automatically) assigned to event variables. The waveform analysis is added to the Edit menu.

Text

Sequence Viewer provides better support for unicode. Communication with word processors like MS Word is improved. Indenting, outdenting and paragraph spacing (which replaces the old 'double space') is supported for the sequence texts. In addition to underlines, other text styles (like italics) are supported.

Word links

A new datatype, word links, is introduced. Word links are simply connections between different words in the sequence text, to indicate that these words are connected in one way or another. Word links can be made visible by an arrow between these words. For the moment word links are primarily intended for qualitative analyses (to indicate relations between text parts), but in future releases also more quantitative analyses will become available.

Other improvements

All setup windows with respect to text analyses are significantly changed, to make them more comparable, that is with similar options and a more similar user interface. Most of these windows have more options, for example to find text with a particular text style.
In many setup windows a new icon is added at the bottom of the window, that enables you to do analyses on checked events only (much like doing analyses on marked sequences only).
And many other improvements, with respect to adding script files, printing, the toolbar, adding new keys (directly in the main sequence window, without having the keys windows open), improved output, improved export and import, and much more.

Solved bugs

Numerous bugs are solved (like not being able to enter replace text in the Find text window). If you encounter a new bug, please report it as soon as possible!

Other changes

The Help file is completely rewritten and updated. Some parts dated from version 4 and were completely outdated. The tutorial is completely rewritten too, and extended with chapters about Waveforms and Word links. Also the reference manual is now uptodate.

June 10, 2012

Changes in Sequence Viewer 5.1a

Solved bugs

• If 'Check event variables' in 'Check data...' ('Sequences' menu) was checked, nothing was checked at all.
• When importing sequence variables ('Import...' from the 'File' menu), the variable type of the imported variables was not set correctly.
• Auto recording of 'Assign sequence number' ('Sequence variables' menu) didn't work.
• Manually changing values of sequence variables in the sequence variables drawer, sometimes caused incorrect values after scrolling through sequence variables.
• Assigning the agreement ('Assign agreement...' from the 'Codes' menu) to a sequence variable didn't work when a sequence definition was applied (all agreements were set to 0).
• Cluster sequences ('Codes' menu) contained a bug, causing the output to become meaningless.
• A large number of minor bugs were solved.

New features

• You can now assign the number of checks of a sequence to a sequence variable ('Assign number of checks...' from the 'Sequence variables' menu).
• In the Export setup window ('File' menu) you can now choose to export checked events only (if appropriate). Moreover, when exporting event codes, you can now add event texts to the event codes.

January 24, 2012

Changes in Sequence Viewer 5.1

Solved bugs

• If changes were made to the dependencies ('Define event codes' from the 'Codes' menu), but no changes to properties of code variables, the 'Define event codes' setup window remained open after clicking 'Store'.
• Changing the 'delay between executing setup lines in Trace mode' in the Sequence Viewer preferences (editor tab), did not change the actual delay.
• In the 'Find text' setup window, if you first selected 'Mark' or 'Unmark', the 'select marked sequences' icon remained disabled, whereas it should become enabled.
• In the 'Find text' setup window, the 'previous setup' icon, did not remember the settings for '(un)checking all events first' or '(un)marking all sequences first' from the previous setup correctly.
• In the main sequence window, the 'go previous marked sequence' button didn't work.
• The (approximate) correspondence between a selected time key and the source text calculated the last word (the approximate correspondence to the end of the key) incorrectly.
• If auto recording of execution scripts was activated, the 'Check random' setup window (available from the 'Sequences' menu), was not automatically recorded.
• Moving a key in the 'Text keys' or 'Time keys' window using the key field slider, was not stored when going to another sequence, or when closing the window.
• If a new Sequence Viewer file was created by importing codes, manually checking or unchecking events was unreliable. The same problem occurred when sequences were copied to other sequences with 'Paste sequences' ('Edit' menu).
• If a new Sequence Viewer file was created, value labels for STARTTIME could not be changed.
• Checking values of event variables in 'Check data...' ('Sequences' menu) was not always correct.
• When you moved the mouse over the help button in the 'Command editor' window, inadequate error messages were sometimes showed in the help field of the toolbar.
• When replacing values of event variables with 'Replace all' of the 'Find value of event variable' setup window, some values were not replaced (in case values should be replaced in successive events).
• And a large number of small annoyances.

New features

• The 'Find keys' setup window ('Keys' menu) is extended with a number of different options, enabling you to find keys that overlap with checked events, and to check or uncheck events that overlap with a particular key.
• With 'auto assign keys' ('Text' menu) you can now find text and assign keys depending on whether (part of) the search text are found in events that are checked.
• With 'Auto code' ('Text' menu) you can now find text in checked events only.
• The import options are now extended with the possibility to import event variables (with or without event codes).
• Sequence and event variables can now be of type 'time stamps' (in addition to 'date' and 'number'). In case of time stamps the values represent the number of seconds since January 1, 1970. The user interface of many windows is adjusted, to allow you to view and edit 'date' and 'time stamp' variables in date or timestamp format.
• The transform event variables and transform sequence variables have a number of new options (related to the introduction of time stamps).
• The 'Change sequence variable' setup window (obtained when you click at a variable name in the sequence variables drawer of the main Sequence window), is extended with a number of useful options.

Improvements

• With the 'Cancel' button in the 'Code dependencies' setup window now only the changes that are made after the last time you opened this window are undone. In previous versions all changes were undone since the 'Define event codes' window was opened.
• In the 'Compute event variable' and 'Compute sequence variable' setup windows, you can now have more then one indexed variable.
• And numerous other minor improvements.

Other changes

• The content of the help file is updated at a number of places.

February 14, 2011

Changes in Sequence Viewer 5.0h

Solved bugs

• In the 'Find event codes' and 'Patterns' setup windows ('Codes' menu) it was not possible to type codes in the event codes fields.
• Adding a sequence, event or code variable with an illegal name, did not give an error message.
• Changes to code dependencies (available from the 'Define event codes' setup window) could not be stored.
• When creating a new file, code variable properties were incorrectly stored.
• When entering your name in the registration window (when opening Sequence Viewer the very first time), spaces were not accepted.

September 15, 2010

Changes in Sequence Viewer 5.0g

Solved bugs

• 'Split sequences' ('Sequences' menu) added all 'before split' subsequences to the file, but only the 'after split' subsequence of the last original sequence.
• In (Snow) Leopard, double clicking a SV file, or dropping the file on the application icon, caused an error message that the file could not be found. This problem was only partly solved in the previous update.
• The Command editor reports syntax errors with 'Text count' (preventing to execute a script using 'text count'), although there are actually no syntax errors.
• If you add a new sequence, event or code variable, the name of the new variable should be different from existing names (e.g. the name of a sequence variable should not be the same as the name of an event variable). However, due to a bug in version 5.0f, you could enter a name that already existed.

June 1, 2010

Changes in Sequence Viewer 5.0f

Solved bugs

• 'Event variables' in the 'Convert keys' setup window ('Keys' menu) could not be enabled, also if event variables were available in the file.
• In (Snow) Leopard, double clicking a SV file, or dropping the file on the application icon, caused an error message that the file could not be found.
• The scrollbar of the source text in the main sequence window was not correctly updated when typing or deleting text.

Improvements

• Events can now also manually be (un)checked in the 'codes only' mode of the main sequence window.
• The command Editor is extended with a number of commands:
  • 'Convert keys' ('Keys' menu), 'Count sequences' ('Codes' menu) and 'Matrix' ('Codes' menu)
  • Manually (un)checking events
  • Selecting the layout mode of the main sequence window
  • Selecting an event variable in the main sequence window
• A large number of small improvements in the user interface.

Other changes

• Part of the application is rewritten in a more efficient way, significantly decreasing the size of the application.
• Due to a change in the development environment, icons no longer have a shadow (to give them a three-dimensional appearance).

March 3, 2010

Changes in Sequence Viewer 5.0e

Solved bugs

• When menu item 'Check random...' from the 'Sequences' menu was selected, nothing happened. In stead a setup window should appear with options for the procedure.
• 'Find value of event variable' did not work correctly when 'Find checked events only' was checked and 'Search all' was selected (the program always selected the first event of a sequence).
• 'Assign empty codes' ('Edit' menu) did not work correctly if double line space was set in the main Sequence window.

Improvements

• 'Check data...' from the 'Sequences' menu is much improved. It provides better and more feedback about the types of errors, the number of errors, more possibilities to quickly correct errors, and better detection of errors.
• In the 'Edit sequence' window ('Edit' menu) you can now hold the option key down when clicking on the 'Add' and 'Insert' buttons, to add or insert the selected event (in stead of an empty event).
• Displaying sequences in the 'codes' and 'codes and event variables' modes was slow in case of long sequences, and many checked events, due to the time it took to show the event checks. This is much faster now.
• More options are available to split sequences ("Split sequences' from the 'Sequences' menu).

February 21, 2010

Changes in Sequence Viewer 5.0d

Solved bugs

• When adding Sequence Viewer files to the present file (File > Import > Add sequence Viewer file(s) to present file), in case of some discrepancies between the sequence variables of the open file and the files that are added, the name of the offending sequence variable was incorrect.

New features

• A menu item 'Check random...' is added to the 'Sequences' menu. With this item you can randomly check events.
• A button 'Neglect' is added to the toolbar. With this button you can select commands from the main sequence window (for example 'Go next sequence'), that will be suppressed (not recorded), when auto recording of scripts is enabled.
• The main Sequence Viewer window now shows the number of checked events in a sequence (just above the 'go previous sequence' icon).

Improvements

• The following commands can now be undone: 'Mark all', 'Unmark all', 'Toggle marks', 'Mark' up' and 'Mark down' from 'Mark sequences' from the 'Sequences' menu; and 'Check all', 'Uncheck all', and 'Toggle checks' from 'Check events' from the 'Sequences' menu; and 'Mark random' and 'Check random' from the 'Sequences' menu.
• The reliability of separate event codes ('Reliability' from the 'Codes' menu) is calculated a bit different, because the old algorithm gave positive kappa's, also in case the expected frequency was lower than the observed frequency. More information about how kappa is calculated is added to the help file.

Other changes

• If a new update is available for download, this is no longer reported in the output window, but by means of an alert box that pops up (you can only observe this of course when the next update becomes available). This is done to prevent that you overlook the message in the output window.

January 14, 2010

Changes in Sequence Viewer 5.0c

Solved bugs

• Adding event times (event variables menu) did not work.
• The reliability analysis did not yield output in case all event codes in a file were equal.
• In some cases the sequence variables drawer could become detached from the main Sequence Viewer window.
• The 'replace with' box of the 'Replace' tab of the 'Find codes' window, did not show the question mark and dash, in case the arrow keys were used to move to different codes in that box.

Improvements

• 'Delete event times' (event variables menu) can now be undone.

December 1, 2009

Changes in Sequence Viewer 5.0b

Solved bugs

• The "Next event" and "Previous event" procedures did not distinguish between uppercase and lowercase codes. This is solved.
• A number of minor bugs were solved.

July 20, 2009

Changes in Sequence Viewer 5.0a

Improvements

• You can now export the start and end of a particular time or text key, with 'Export' from the 'File' menu.

Solved bugs

• Deleting marked sequences ('Delete sequences' from the 'Sequences' menu) did not work correctly.
• Sorting sequences ('Sort sequences' from the 'Sequences' menu) made all sequences disappear.
• The titlebar of the output window and the main sequence window, could be moved behind the toolbar, making access to these windows difficult. Now you can no longer move these windows behind the toolbar.

July 6, 2009

Changes in Sequence Viewer 5.0

Sequence Viewer 5 has numerous new options and other improvements. Only the most important ones are described below. Moreover, the file structure is changed (primarily to account for the new time and text keys structure). As a consequence, files created by Sequence Viewer 5.x cannot be read by Sequence Viewer 3.x and 4.x. Files created by version 3.x or 4.x however can simply be read by Sequence Viewer 5.x, and are saved in the new format.

New features

Event checks

• You can now check and uncheck events (similar to marking and unmarking sequences, but now for separate events). To (un)check an event manually, you can click before the event code in the main sequence window.
• The 'Sequences' menu has a new menu item, 'Check events' with subitems to check, uncheck and toggle event checks.
• The 'Find event codes' and 'Find value of event variable' setup windows are extended to (un)check events and to find (un)checked events.
• The sequence definition is extended with a new option to have only the (un)checked events of a sequence.

Other new features

• Sequence Viewer now has a toolbar (in the upper left corner of the screen. This toolbar contains options to automatically record scripts, run scripts, underline texts and inserts special symbols, and has a help field (which replaces the extended window at the bottom of setup windows).
• A menu item 'Toolbar' is added to the 'Edit' menu, enabling you to show/hide the different parts of the toolbar.
• A menu item 'Keyword length...' is added to the keys menu. The setup window let's you calculate the average and frequencies of the length of text keys (the number of words) and time keys (the duration of the key).

Improvements

The (time and text) keys window is dramatically improved. Now there is only one mode (in stead of a separate edit and view mode), where you can both edit and view the keys. Editing is much more simple and intuitive. There are no longer markers; in stead you can directly move, split, and combine keys. In the previous version, only four keys could be added to a marker, and hence only four keys could start at a particular point. Now the number of keys starting at a particular point is unlimited. Also the number of different keys in a sequence is now unlimited. A new menu item, 'Define keys', is added to the 'Keys' menu, to change properties of keys, like color and names. The main sequence window has some more options to display keys (in the keys box in the lower right corner).

Solved bugs

Numerous bugs were solved, including the bugs reported by users. If you encounter a new bug, please report it as soon as possible!

Other changes

• Many changes to the user interface to make it more consistent. Copy and paste has become more smart, to prevent incorrect data entry (e.g. if you copy '12a34' and paste it in a field where only numbers are allowed, it will paste '1234').
• The Tutorial has been completely rewritten, and is extended with new chapters, including how to work with keys and with scripts. Also the reference manual and the online help are updated to account for the new version.

Back to Sequence Viewer

Changes in previous versions