Home > Support > Bugs


Application: Studio
Version: v6.0
Tool: All

Records found: 16

Status: P: Pending, S: Suspended, C: Corrected, R: Not reproductible.

Select bug id:
Description contains:
Select application:
Select application version:
Select tool:

Tool acronyms: IN: Installation, LM: License management, UE: UML editor, ME: MSC editor, TE: Text editor, SE: SDL-RT editor, PM: Project manager, PG: Prototyping GUI, CG: C code generator, MT: MSC tracer, MD: Model Debugger, MS: Model Simulator, MV: Model validation, DE: Document editor, TT: TTCN-3 support

Tool id description comment date status forecast
*
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
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
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
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 
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  
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 
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
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
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
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