|
Application: Studio Version: v6.0 Tool: All Records found: 50 Status: P: Pending, S: Suspended, C: Corrected, R: Not reproductible. |
| Tool | id | description | comment | date | status | forecast |
|---|---|---|---|---|---|---|
| * Lin | 4695 | When using Wayland, if a window menu is displayed, clicking the close button of this window triggers an unexpected error. | This does not happen with X11, where the menu is erased as soon as the mouse button is clicked anywhere. Looks like a Wayland issue. | 2023-11-17 | P | |
| * | 4692 | On Windows, if an editor window is opened and has a dialog attached to it, closing the project manager window works, and starts to close all windows, including this one, which may cause crashes since it's in the middle of something. | Corrected. There has always been a similar issue on Linux, so the same solution was used. | 2023-11-15 | C | v6.1 |
| * | 4642 | Some translations don't work: the entry is present in the translation file, but the text displayed in the application is always the english text. | Corrected. Some texts were internationalized before the translator was actually initialized, causing them to stay in english. The initialization of the translator has been moved at an earlier stage to prevent this from happening. | 2023-05-05 | C | v6.0.2 |
| * Win | 4631 | If any element in an opened editor is not saved, trying to close all windows with the task bar menu can get everything stuck: the window with the modified element is brought to the front, but no Save/Discard/Cancel dialog appears, and all windows are unresponsive. | Corrected. The reason why the save confirmation dialog wasn't appearing is unclear, but its display is forced now, and it should appear in all cases. For versions before 6.0.2, a workaround is to minimize all windows, for example using the keyboard shortcut Windows+M; this causes the Save/Discard/Cancel dialog to appear. | 2023-04-11 | C | v6.0.2 |
| * | 4627 | A corrupted preferences file can trigger unexpected errors during a lot of operations. | 2023-03-16 | P | ||
| * | 4506 | A non-readable internal data directory .rtds_data may cause unexpected errors when opening projects or its elements. | Corrected. The problem was mostly with crash-saved files: their existence was tested before opening the element, but this failed when the directory was not readable. This case is now correctly handled and the contents of the unreadable directory is just ignored. | 2022-11-24 | C | v6.0.1 |
| * Win | 4485 | A message is displayed via a "vanishing notification panel" (a temporary yellow rectangle displaying the message) may cause an unexpected error on Windows. | Corrected. The name of the default font on Windows may contain a space, which was not considered in this case, which could cause the error. | 2022-08-23 | C | v6.0.1 |
| *E | 4719 | If a default zoom factor is defined in the preferences, opening a diagram in a new tab of an exisiting editor doesn't consider it. | Corrected. The default zoom factor was applied to the first diagram opened in the editor, but not to the next ones. | 2023-12-20 | C | v6.1 |
| *E | 4511 | In some unidentified cases, opening a file with a name containing non-ASCII characters, or opening a file when another one with non-ASCII characters in its name is already opened can cause an unexpected error. | Corrected. This happened during the update of the 'Windows' menu, where somehow, some files were correctly encoded and others weren't. Sorting them to put them in the menu was triggering the error. | 2022-12-07 | C | v6.0.1 |
| *E | 4487 | Code completion does not work properly when there are blank lines after a declaration: for example, if a synonym is declared on one line, then there is a blank line, and "syn" is typed, the popup listing "synonym" & "syntype" as possible completions does not appear. It works if there is no blank line. | Corrected. In this particular case, the prefix for the inserted keyword was not identified correctly and ended up including an initial new line character, which caused all possible choices to be discarded because they weren't starting with the prefix. | 2022-08-31 | C | v6.0.1 |
| CG | 4498 | The "RTOS-less" code generation profiles used for scheduling are not marked as supporting the SDL broadcast, so trying to generate the code for scheduling for a system doing a broadcast fails. But it should work: all the necessary macros are defined and th broadcast works with these profiles. | Corrected. The option indicating that broadcast is supported was not correctly sets for these profiles. | 2022-11-09 | C | v6.0.1 |
| ME | 4729 | Operation return links in MSC diagrams can end up reversed: if the link is created from lifeline A to lifeline B, after saving, closing and reopening, the link may appear to go from lifeline B to lifeline A. | 2024-01-12 | P | ||
| ME | 4705 | Exporting a MSC diagram that contains non-ASCII characters as a MSC-PR file might end up in an unexpected error. | Corrected. The encoding of the generated file was not handled correctly. | 2023-12-05 | C | v6.1 |
| ME | 4622 | When comparing MSC diagrams where one of them has collapsed lifelines, the diff reports the original lifelines as missing from the other MSC, when they are no more visible in the first one. | Corrected. A diff for a lifeline present in either of the diagrams, but not in the other one is now no more reported if the existing lifeline is hidden (i.e, collapsed into another one). | 2023-03-15 | C | v6.0.2 |
| ME | 4614 | If a diff is launched on an already opened MSC diagram displayed with a zoom factor that is not 100%, the diff markers are off. | Corrected. The diff markers are now displayed correctly whether the diagrams were opened before the diff or not and whatever the zoom factor is. | 2023-03-14 | C | v6.0.2 |
| ME | 4611 | If a locked MSC diagram is selected as the second diagram is a MSC diff, the attempt to open it shows the standard "Locked file" dialog as expected. But selecting "Cancel" in this dialog seems to try to proceed with the diff anyway, and triggers an unexpected error because the diagram has not been opened. | Corrected. If the opening of one of the diagram fails for whatever reason, the diff is now cancelled. | 2023-03-13 | C | v6.0.2 |
| ME | 4623 | It is possible to create message links that start and/or end after the end of the lifeline sending/receiving them, leading to message links with one or both ends not attached to any lifeline at all. | 2023-03-13 | P | ||
| ME | 4502 | While doing a MSC diff, if the zoom level is changed, the markings for the added/modified/deleted items disappear. They reappear when moving through the differences, but they are "off": they don't appear around the item with the difference. | Corrected. The highlighted positions were not restored after a zoom level change, and they were displayed at zoom level 100% whatever the zoom level for the diagram was. | 2022-11-10 | C | v6.0.1 |
| ME | 4497 | When checking a PSC property against a MSC diagram containing collapsed lifelines, it happens that the highlights on the MSC are off compared to the actual compared event. | The problem is not the collapsed lifelines; see bug n. 4502 for the real problem. | 2022-11-08 | R | |
| ME | 4496 | When collapsing lifelines, messages to the collapsed lifeline may get corrupted: after saving the diagram and reloading it, they might display as links from the sender to itself. | Corrected. The problem was actually when the diagram was saved: internally, the destination for the message is not the collapsed lifeline, but the lifeline it "contains", and there was a wrong test on this criterion when saving, causing the event for the message reception to be attached to the sender instead of the receiver. | 2022-11-08 | C | v6.0.1 |
| MS | 4708 | Trying to run a prototyping GUI when its file is unreadable for any reason ends up in an unexpected error. | Corrected. This case was not properly handled. | 2023-12-05 | C | v6.1 |
| MS | 4613 | There are multiple issues with state timers when the delay for the timer is changed during the transition: if the transition ends with a 'NEXTSTATE -', the timer is restarted with its previous delay value and not the new one, and if the transition ends with a 'NEXTSTATE' on its initial state, the timer sometimes appear to time out after a wrong delay. | Corrected. The handling of state timers was made for one part inside the bytecode and for another part in the bytecode executor, which caused the issues. State timers are now completely handled within the generated bytecode, allowing to handle correctly updated delays in all cases. | 2023-03-15 | C | v6.0.2 |
| MS | 4612 | State timers defined via the syntax 'STATE TIMER now + delay' don't seem to work at all. | Temporary fix: the STATE TIMER syntax has been disabled. If it is used, the syntax check will issue an error message saying to use the SET(...) syntax for state timers. | 2023-03-13 | P | v6.0.2 |
| MS | 4521 | If a TTCN testcase contains an execute statement for another testcase - which is invalid in this context -, the error is not spotted by the syntax/semantics check and trying to generate the bytecode ends up in an unexpected error. | Corrected. The error is now spotted at bytecode-generation and will display a proper error message. | 2022-12-30 | C | v6.0.1 |
| MS | 4500 | When an input symbol is modified to reference a different message from the previous one, if a simulation is launched right after saving the diagram, the bytecode generation fails with an "internal error" message referencing both the new message and the old one. | Corrected. An internal structure listing the messages received by the symbol was read before the new text was taken into account, causing the old message to stay referenced as incoming for the symbol, which caused the error during bytecode generation. | 2022-11-09 | C | v6.0.1 |
| MV | 4528 | When trying to explore a system with an input message that has a parameter whose value is not limited, the exploration runs anyway and stops after a few steps with no error message. This case should be spotted before running anything and the exploration should not even start. | Partially corrected. The check is not yet done before the exploration starts, so it runs anyway. But if the problem occurs, the exploration stops and displays an error message saying what the problem is. See feature 4531. | 2023-01-11 | C | v6.0.1 |
| MV | 4530 | In an OBP exploration profile, if the constraints set for a parameter value include values that are outside of the parameter type's range, an unexpected error may occur. | Corrected. All values allowed by the constraints were considered, even those that were not valid, causing the error when the parameter was actually set to the invalid value. | 2023-01-11 | C | v6.0.1 |
| PM | 4715 | Trying to edit the performance properties in a system containing a process with a priority input symbol causes an unexpected error. | Corrected. The same was happening when a process contained a priority output symbol. These two symbol types were not handled correctly. | 2023-12-13 | C | v6.2 |
| PM | 4710 | When using the free version, if an "import directory" from the project manager would create a project that exceeds the limitations, an unexpected error occurs instead of an error message. | 2023-12-05 | P | v6.1 | |
| PM | 4709 | If a diagram has partitions stored in their own files, but one of these files is missing or unreadable, trying to rename the diagram from the project manager ends up in an unexpected error. | 2023-12-05 | P | v6.1 | |
| PM | 4697 | When the application language is not English, the "Font DPI" preference does not behave correctly: selecting the equivalent of "Default" does not disable the DPI value entry and internally, the preference statys at "Forced" and considers the value in the entry. NB: this prevents the display scaling from working on Windows. | Corrected. This was an application translation issue: the translated text corresponding to "Default" was not recognized as the default in the preferences dialog, causing the "Forced" option to still be selected. | 2023-11-20 | C | v6.1 |
| PM | 4618 | Exporting a system with processes at system level fails. This is based on an old version of the SDL standard; the latest one allows processes at system-level, so the export should work. | Corrected. To be able to keep the former behavior, an option has been added called "Strict SDL-96" conformance, which defaults to true but can be unchecked at export, or configured to false by default in the preferences. If it is unchecked, processes will be allowed at system level, as well as mixing blocks and processes in the same system or block. | 2023-03-13 | C | v6.0.2 |
| PM | 4558 | After an unexpected error while the project was not saved, trying to switch to its crash-saved version when reopening it sometimes causes a new unexpected error. | Corrected. The problem is probably that saving the crash-saved version failed after the first error, and there's no file for the version to switch to. This issue is now handled properly: an error message is displayed in this case. | 2023-02-02 | C | v6.1 |
| PM | 4557 | In the generation options wizard, if nothing is chosen the 'OK' button is correctly inactive, but pressing the return key validates the dialog anyway, causing an unexpected error. | Corrected. This probably happened with other dialogs as well: the binding on the 'return' key was validating the dialog whether the 'OK' button was active or not. The button state is now tested and nothing happens if it's inactive. | 2023-02-02 | C | v6.1 |
| PM | 4547 | Exporting as PR a project containing a block class that has channels inside it connected to its outer frame, but specify no gate name triggers an unexpected error. | Corrected. These channels actually must have a gate name and not having one is identified as an error by the syntax/semantics check. But the PR export doesn't check that beforehand, and was getting confused by the missing gate name. The channle is now exported in the PR file with no gate name either. | 2023-01-24 | C | v6.1 |
| PM | 4546 | A project containing SDL-RT diagrams as well as UML class diagrams with classes used by the SDL-RT system triggers an unexpected error when exported to a PR file. | Corrected. This actually prevents the export to be done, as passive classes have no representation in PR. | 2023-01-24 | C | v6.1 |
| PM | 4533 | When converting a PR/CIF file with the free version, an unexpected error may occur if one of the converted behavioral diagram is very close to the size limitation. | Corrected. The conversion process actually generates legacy behavioral diagram and then converts them to new-style. The problem was happening if the converted diagram was above the size limit. The correction was to simply keep the diagram in legacy format if that happens. | 2023-01-12 | C | v6.1 |
| PM | 4509 | When generating TTCN test cases from MSCs, if one of them contains a lifeline with a completely blank text, an unexpected error occurs. | Corrected. The first word of the text was considered to be the name for the element represented by the lifeline, but its extraction wasn't working when the lifeline text was empty. | 2022-12-06 | C | v6.0.1 |
| PM | 4508 | When trying to convert a SDL-PR/CIF file to a Studio project, if the chosen destination directory is not writable by the current user, an unexpected error occurs. | Corrected. The error was not handled properly. | 2022-12-06 | C | v6.0.1 |
| PM | 4490 | When a diagram is opened alone, there is actually a temporary project loaded in the project manager that has no file name. This might cause unexpected errors in some features, such as exporting the project to HTML, where the project file name is used as a base for the export. | Corrected. There was also a problem with the "save a copy" feature on unnamed projects, which has been fixed too. | 2022-09-05 | C | v6.0.1 |
| PM | 4486 | When importing a SDL-PR file, if an agent contains an invalid symbol - e.g. a STOP in a procedure -, the error is not handled properly and an unexpected error might occur. | Corrected. This particular error case was not correctly handled. | 2022-08-24 | C | v6.0.1 |
| PM | 4481 | If for any reason, the executable for PLM_Manager has no execution permission, trying to call it from the Project Manager using "Studio" -> "Manage PLM licenses..." triggers an unexpected error. | Corrected. The problem is now handled correctly and an error message is displayed to the user. | 2022-08-11 | C | v6.0.1 |
| PM Win | 4478 | When element file locking is enabled, if file names contain non-ASCII characters, an unexpected error may occur when editors are closed, caused by the attempt to unlock the file. | Corrected. An invisible file has to be deleted when the element is unlocked, and Windows requires to make it visible again to be able to delete it. There was a file name encoding issue there, which could cause an unexpected error. | 2022-08-05 | C | v6.0.1 |
| SE | 4702 | The default/custom selector for symbol and link colors works badly in the behavioral editors: the first click seems to do nothing, and it has to be clicked twice to actually switch the indicator and open the color selection dialog if 'custom' is clicked. | 2023-11-24 | P | ||
| SE | 4624 | In a behavioral diagram, it is not possible to attach a comment to a save symbol. | Corrected. Everything was working internally, but the button to insert a comment was wrongly disabled in the editor when a save symbol was selected. | 2023-03-14 | C | v6.0.2 |
| SE | 4501 | When opening behavioral diagrams, it happens that a duplicate 'Help' menu is created in the window and inserted at the first position in the menu bar. | Corrected. This actually happened each time a simulator or debugger was launched: in this case, a 'Debug' menu is created in the editor window which should be inserted just before the 'Help' menu. This was not done correctly, causing the 'Help' menu to sometimes be duplicated in weird positions. | 2022-11-10 | C | v6.0.1 |
| SE | 4484 | When inserting symbols in the behavioral diagram editor, it happens that the insertion button stays enabled for a little time just after an insertion, which allows to click on it again if it's done right after the first click. This causes invalid diagrams to be created, like a state symbol directly following a state symbol, or even unexpected errors. | Corrected. There were actually some cases where the button was always staying active, even when it looked inactive (grayed out). The button action is now fired only when the button is enabled, and it is disbaled as soon as it needs to be. | 2022-08-23 | C | v6.0.1 |
| UD | 4619 | In paragraph 2.3.3.3 of the User Manual, it is specified that the "lifeline dies/survives" symbol toggles the instance tail / instance stop symbol at the end of the lifeline. This is incorrect: it can be used to insert a stop symbol, which can be removed by using the contextual menu. | Corrected. The confusion was coming from the fact that this feature works in a different way in new-styule & legacy diagrams. The text has been change to make it clearer. | 2023-03-15 | C | v6.0.2 |
| UD | 4615 | In the Reference Manual, in the part about experimental exports (section 20), there are references to SDL 'signalroutes', which are not supported by the application and have disappeared from the standard. | Corrected. The translation tables now only list channels. | 2023-03-13 | C | v6.0.2 |
| UD | 4621 | The description of the remote variable feature in SDL is missing from the reference manual. | Corrected. The description of remote variables has been added in the section describing the "Text" symbol in the "Behavior" part of the "SDL refrence guide" (section 3.4.1). | 2023-03-13 | C | v6.0.2 |