Menu
▾
▴
scstudio-devel — Development mailing list
You can subscribe to this list here.
| 2009 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
(11) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(10) |
| 2011 |
Jan
(12) |
Feb
(4) |
Mar
(29) |
Apr
(4) |
May
(5) |
Jun
(5) |
Jul
(34) |
Aug
(14) |
Sep
(1) |
Oct
|
Nov
(29) |
Dec
(7) |
| 2012 |
Jan
(17) |
Feb
(3) |
Mar
(5) |
Apr
(3) |
May
(2) |
Jun
(9) |
Jul
(67) |
Aug
(5) |
Sep
(6) |
Oct
(14) |
Nov
(3) |
Dec
(1) |
| 2013 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: SourceForge.net <no...@so...> - 2011-11-29 16:27:39
|
Bugs item #3067517, was opened at 2010-09-16 04:26 Message generated for change (Comment added) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3067517&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open >Resolution: None Priority: 5 Private: No Submitted By: Vojtech Rehak (xrehak) >Assigned to: Martin Bezděka (mbezdeka) Summary: Large numbers in time constraints - visio deformation Initial Comment: When a visio drawing is redrawn from internal structure (repaint, result presentation), large numbers are deformed into exponential form, i.e. 1.23453e+12. ---------------------------------------------------------------------- >Comment By: Ondřej Bouda (obouda) Date: 2011-11-29 08:27 Message: ...in other words, the expected behavior is that Visio prints the number as precisely as possible. For the example below, the number 123456789012 should be displayed exactly as 123456789012. The double datatype stores about 15 decimal digits, so it should not be a problem. ---------------------------------------------------------------------- Comment By: Ondřej Bouda (obouda) Date: 2011-11-27 16:28 Message: The type numbers are converted to is double, Which means that numbers like 12345789012 should not be parsed without loss of precision. Which means such a number is still stored exactly as specified, but only presented with precision loss. Which means this is rather an annoyance in the frontend. ---------------------------------------------------------------------- Comment By: Vojtech Rehak (xrehak) Date: 2010-11-01 07:36 Message: It is OK for now. For the future, we need to note somewhere what is the exact precision we are working with. The problem is that Martin Vodila is currently working on extraction of bMSC from test logs and he decided to use unix time in milliseconds which I guess is out of our current precision. ---------------------------------------------------------------------- Comment By: Petr Gotthard (gotthardp) Date: 2010-09-21 00:52 Message: This is not a bug. This is a feature. Exponential form is (now) correctly handled by parser. Is there anything that we should fix here? What is the desired behaviour? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3067517&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-29 09:02:29
|
Bugs item #3132755, was opened at 2010-12-08 16:31 Message generated for change (Comment added) made by xrehak You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3132755&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open Resolution: None Priority: 4 Private: No Submitted By: Vojtech Rehak (xrehak) Assigned to: Petr Gotthard (gotthardp) Summary: Wrong filename in warnig when importing an empty file. Initial Comment: When importing an empty file, the following warning is printed: Import failed. Cannot load file 'C:.mpr'. where the file name is corrupted. ( This message is printed from src/view/visio/addon/document.cpp line 2065 m_reportView->Print(RS_ERROR, stringize() << "Import failed. Cannot load '" << TOWSTRING(filename) << "'."); ) ---------------------------------------------------------------------- >Comment By: Vojtech Rehak (xrehak) Date: 2011-11-29 01:02 Message: The value in filename is correct. The problem is caused by backslashes in the string, they are interpreted as special characters. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3132755&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-28 08:29:50
|
Bugs item #3443561, was opened at 2011-11-27 15:42 Message generated for change (Settings changed) made by xrehak You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3443561&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Beautify Group: None Status: Open Resolution: None Priority: 9 Private: No Submitted By: Ondřej Bouda (obouda) >Assigned to: Milan Malota (xmalota) Summary: Beautify destroys other pages' contents Initial Comment: When there are several pages in the document, Beautify, run on one page, beautifies the active pages correctly, but blanks all the other pages. See the supplied example cons_neg_36.vsd to reproduce: 1. Open the document, see that there is something on pages "Page-1" and "b" 2. Switch to page "a" 3. Run Beautify (either via menu, icon or a keyboard shortcut) 4. Switch to page "Page-1" or "b" While the pages "Page-1" and "b" should also be beautified, they are blank. Note that when Beautify is run on page "Page-1", the other pages are also beautified, as expected. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3443561&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-28 00:29:16
|
Bugs item #3067517, was opened at 2010-09-16 04:26 Message generated for change (Settings changed) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3067517&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: Visio Interface Group: None Status: Open Resolution: Wont Fix Priority: 5 Private: No Submitted By: Vojtech Rehak (xrehak) Assigned to: Martin Vodila (martinnrt) Summary: Large numbers in time constraints - visio deformation Initial Comment: When a visio drawing is redrawn from internal structure (repaint, result presentation), large numbers are deformed into exponential form, i.e. 1.23453e+12. ---------------------------------------------------------------------- Comment By: Ondřej Bouda (obouda) Date: 2011-11-27 16:28 Message: The type numbers are converted to is double, Which means that numbers like 12345789012 should not be parsed without loss of precision. Which means such a number is still stored exactly as specified, but only presented with precision loss. Which means this is rather an annoyance in the frontend. ---------------------------------------------------------------------- Comment By: Vojtech Rehak (xrehak) Date: 2010-11-01 07:36 Message: It is OK for now. For the future, we need to note somewhere what is the exact precision we are working with. The problem is that Martin Vodila is currently working on extraction of bMSC from test logs and he decided to use unix time in milliseconds which I guess is out of our current precision. ---------------------------------------------------------------------- Comment By: Petr Gotthard (gotthardp) Date: 2010-09-21 00:52 Message: This is not a bug. This is a feature. Exponential form is (now) correctly handled by parser. Is there anything that we should fix here? What is the desired behaviour? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3067517&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-28 00:28:56
|
Bugs item #3067517, was opened at 2010-09-16 04:26 Message generated for change (Comment added) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3067517&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: Wont Fix Priority: 5 Private: No Submitted By: Vojtech Rehak (xrehak) Assigned to: Martin Vodila (martinnrt) Summary: Large numbers in time constraints - visio deformation Initial Comment: When a visio drawing is redrawn from internal structure (repaint, result presentation), large numbers are deformed into exponential form, i.e. 1.23453e+12. ---------------------------------------------------------------------- >Comment By: Ondřej Bouda (obouda) Date: 2011-11-27 16:28 Message: The type numbers are converted to is double, Which means that numbers like 12345789012 should not be parsed without loss of precision. Which means such a number is still stored exactly as specified, but only presented with precision loss. Which means this is rather an annoyance in the frontend. ---------------------------------------------------------------------- Comment By: Vojtech Rehak (xrehak) Date: 2010-11-01 07:36 Message: It is OK for now. For the future, we need to note somewhere what is the exact precision we are working with. The problem is that Martin Vodila is currently working on extraction of bMSC from test logs and he decided to use unix time in milliseconds which I guess is out of our current precision. ---------------------------------------------------------------------- Comment By: Petr Gotthard (gotthardp) Date: 2010-09-21 00:52 Message: This is not a bug. This is a feature. Exponential form is (now) correctly handled by parser. Is there anything that we should fix here? What is the desired behaviour? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3067517&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-27 23:52:17
|
Bugs item #3071879, was opened at 2010-09-20 05:31 Message generated for change (Comment added) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3071879&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open Resolution: None Priority: 2 Private: No Submitted By: Martin Chmelík (agmy) Assigned to: Martin Bezděka (mbezdeka) Summary: Shapes are having too thin lines Initial Comment: When exporting to bitmap formats the lines are too thin. In lower resolutions even not displayed at all. ---------------------------------------------------------------------- >Comment By: Ondřej Bouda (obouda) Date: 2011-11-27 15:52 Message: Any reasonable example? Seems OK from what I have tried so far... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3071879&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-27 23:51:16
|
Bugs item #3132755, was opened at 2010-12-08 16:31 Message generated for change (Settings changed) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3132755&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open Resolution: None >Priority: 4 Private: No Submitted By: Vojtech Rehak (xrehak) Assigned to: Petr Gotthard (gotthardp) Summary: Wrong filename in warnig when importing an empty file. Initial Comment: When importing an empty file, the following warning is printed: Import failed. Cannot load file 'C:.mpr'. where the file name is corrupted. ( This message is printed from src/view/visio/addon/document.cpp line 2065 m_reportView->Print(RS_ERROR, stringize() << "Import failed. Cannot load '" << TOWSTRING(filename) << "'."); ) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3132755&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-27 23:42:46
|
Bugs item #3443561, was opened at 2011-11-27 15:42 Message generated for change (Tracker Item Submitted) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3443561&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Beautify Group: None Status: Open Resolution: None Priority: 9 Private: No Submitted By: Ondřej Bouda (obouda) Assigned to: Nobody/Anonymous (nobody) Summary: Beautify destroys other pages' contents Initial Comment: When there are several pages in the document, Beautify, run on one page, beautifies the active pages correctly, but blanks all the other pages. See the supplied example cons_neg_36.vsd to reproduce: 1. Open the document, see that there is something on pages "Page-1" and "b" 2. Switch to page "a" 3. Run Beautify (either via menu, icon or a keyboard shortcut) 4. Switch to page "Page-1" or "b" While the pages "Page-1" and "b" should also be beautified, they are blank. Note that when Beautify is run on page "Page-1", the other pages are also beautified, as expected. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3443561&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-26 22:41:30
|
Bugs item #3367960, was opened at 2011-07-15 06:26 Message generated for change (Settings changed) made by lkorenciak You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3367960&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Verification algorithms Group: None >Status: Closed Resolution: None Priority: 9 Private: No Submitted By: Vojtech Rehak (xrehak) Assigned to: Lubos Korenciak (lkorenciak) Summary: Time Consistent Checker Crash Initial Comment: Time consistent checker crashes on the attached input file. On Windows, it crashes Visio. On linux: checker_test" "..?../check/time/libsctime.so" "Time Consistent" ~/Fail.mpr "1" returns: checker_test: /usr/include/boost/smart_ptr/intrusive_ptr.hpp:166: T* boost::intrusive_ptr<T>::operator->() const [with T = BMsc]: Assertion `px != 0' failed. Aborted ---------------------------------------------------------------------- >Comment By: Lubos Korenciak (lkorenciak) Date: 2011-11-26 14:41 Message: fixed by commit 1210 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3367960&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-26 11:17:11
|
Bugs item #3198221, was opened at 2011-03-02 23:56 Message generated for change (Comment added) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3198221&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Verification algorithms Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Lubos Korenciak (lkorenciak) Assigned to: Kocian (kocianon) Summary: Time consistency algorithm is not working Initial Comment: Time consistency finds inconsistency in consistent BMSC (see attached file). ---------------------------------------------------------------------- >Comment By: Ondřej Bouda (obouda) Date: 2011-11-26 03:17 Message: Seems OK in the current version. ---------------------------------------------------------------------- Comment By: Lubos Korenciak (lkorenciak) Date: 2011-05-19 02:41 Message: This bug is caused by empty BMSCs referenced by MSG nodes with time constraints. According to definition the time constraint attached to MSG reference node without events should be ignored. SCStudio currently does not ignore them and finds inconsistency caused by these constraints. Note, that this bug can be easily solved by preprocessing. It is possible to erase these constraints before running the time algorithms and everything should work correctly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3198221&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-26 03:11:33
|
Bugs item #3368705, was opened at 2011-07-16 05:45 Message generated for change (Comment added) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3368705&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open Resolution: None >Priority: 6 Private: No Submitted By: Martin Bezděka (mbezdeka) Assigned to: Nobody/Anonymous (nobody) Summary: Scstudio fires every visio event twice Initial Comment: All visio events like mouseDown, selectionChange,... are fired twice. ---------------------------------------------------------------------- >Comment By: Ondřej Bouda (obouda) Date: 2011-11-25 19:11 Message: Is it really a blocking bug, when the frontend is usable? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3368705&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-26 03:07:47
|
Bugs item #3435701, was opened at 2011-11-09 11:16 Message generated for change (Settings changed) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3435701&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open Resolution: None >Priority: 7 Private: No Submitted By: Ondřej Bouda (obouda) Assigned to: Martin Bezděka (mbezdeka) Summary: Context menu not available for all pages except the first Initial Comment: The SCStudio context menu for the paper (containing items such as Add Instances, Message Numbering, etc.) is only available on the first page of the drawing. On other pages the menu is not there (both right after creating that page, and after loading an existing document). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3435701&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-26 03:02:12
|
Bugs item #3346100, was opened at 2011-06-30 01:14 Message generated for change (Comment added) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3346100&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: Radek Sedláček (rsedlac) Assigned to: Martin Bezděka (mbezdeka) Summary: Spaces in condition nodes Initial Comment: SCStudio reports an error if the text in condition nodes contains spaces. ---------------------------------------------------------------------- >Comment By: Ondřej Bouda (obouda) Date: 2011-11-25 19:02 Message: Regarding the last comment, a condition name should really only consist of alphanumeric characters and underlines and dots, as it is syntactically the same as <name> ::= {<letter> | <decimal digit> | <underline> | <full stop>}+ However, it would be useful for users to specify a free text in the condition, just for documentation purposes - then, the condition might be always evaluated to true. Therefore, the following should be done: 1) BMSC conditions should forbid any characters other than {<letter> | <decimal digit> | <underline> | <full stop>}+ 2) For both BMSC and HMSC, a more explaining error should be generated, something like "condition name can only contain letters, digits, underlines or full stops". 3) An extension to the standard should be implemented: a string enclosed in double quotes should be allowed as an additional value type of the condition text. Such a string may contain anything except double quotes. Semantics: a condition containing such a string should always be evaluated to true. ---------------------------------------------------------------------- Comment By: Ondřej Bouda (obouda) Date: 2011-11-25 18:42 Message: The behavior is different in BMSC and in HMSC. In BMSC, even a condition node containing spaces is verified OK. In HMSC, an error is reported on a condition node containing spaces, although quite confusing. For example, an HMSC containing just start symbol connected to a condition containing spaces, connected to a reference node, connected to an end symbol, the following errors are reported: 1) Bad condition: expecting next state name 2) Wrongly attached connector. 3) Wrongly attached connector. 4) Verification failed. Graphical errors in the drawing. The reason for such a set of errors is that the parser probably does not connect the condition node containing spaces with other elements. The problems are the following: 1) The behavior should be the same for BMSC and HMSC. 2) According to the ITU-T Z.120, section Condition, the condition text should (among others) contain a condition name list, which may consist of one or more condition names. A condition name is not defined anywhere, though, so basically there is no reason for forbidding spaces. Thus, spaces should be allowed in condition names. 3) Should spaces be forbidden in the condition names, a more explaining error message should be reported, at least. ---------------------------------------------------------------------- Comment By: Martin Bezděka (mbezdeka) Date: 2011-07-08 04:06 Message: Ok, according to previous comment, this isn't error, but feature. If not, please specifiy the problem again. ---------------------------------------------------------------------- Comment By: Vojtech Rehak (xrehak) Date: 2011-06-30 02:38 Message: According to the ITU Z.120 specification, the text is specified as depicted in the attached picture. Therefore, it is a condition expression or condition name rather than a long text description. The reported error says that spaces are not supported in condition names. The underline and dot is allowed. For more info how to use conditions see, e.g., www.itu.int/ITU-T/2005-2008/com17/languages/Z120.pdf pages 42-44 (44-46 in the PDF). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3346100&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-26 02:42:53
|
Bugs item #3346100, was opened at 2011-06-30 01:14 Message generated for change (Comment added) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3346100&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open Resolution: None >Priority: 7 Private: No Submitted By: Radek Sedláček (rsedlac) Assigned to: Martin Bezděka (mbezdeka) Summary: Spaces in condition nodes Initial Comment: SCStudio reports an error if the text in condition nodes contains spaces. ---------------------------------------------------------------------- >Comment By: Ondřej Bouda (obouda) Date: 2011-11-25 18:42 Message: The behavior is different in BMSC and in HMSC. In BMSC, even a condition node containing spaces is verified OK. In HMSC, an error is reported on a condition node containing spaces, although quite confusing. For example, an HMSC containing just start symbol connected to a condition containing spaces, connected to a reference node, connected to an end symbol, the following errors are reported: 1) Bad condition: expecting next state name 2) Wrongly attached connector. 3) Wrongly attached connector. 4) Verification failed. Graphical errors in the drawing. The reason for such a set of errors is that the parser probably does not connect the condition node containing spaces with other elements. The problems are the following: 1) The behavior should be the same for BMSC and HMSC. 2) According to the ITU-T Z.120, section Condition, the condition text should (among others) contain a condition name list, which may consist of one or more condition names. A condition name is not defined anywhere, though, so basically there is no reason for forbidding spaces. Thus, spaces should be allowed in condition names. 3) Should spaces be forbidden in the condition names, a more explaining error message should be reported, at least. ---------------------------------------------------------------------- Comment By: Martin Bezděka (mbezdeka) Date: 2011-07-08 04:06 Message: Ok, according to previous comment, this isn't error, but feature. If not, please specifiy the problem again. ---------------------------------------------------------------------- Comment By: Vojtech Rehak (xrehak) Date: 2011-06-30 02:38 Message: According to the ITU Z.120 specification, the text is specified as depicted in the attached picture. Therefore, it is a condition expression or condition name rather than a long text description. The reported error says that spaces are not supported in condition names. The underline and dot is allowed. For more info how to use conditions see, e.g., www.itu.int/ITU-T/2005-2008/com17/languages/Z120.pdf pages 42-44 (44-46 in the PDF). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3346100&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-11 00:41:50
|
Feature Requests item #3436280, was opened at 2011-11-10 16:41 Message generated for change (Tracker Item Submitted) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046489&aid=3436280&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open Priority: 3 Private: No Submitted By: Ondřej Bouda (obouda) Assigned to: Nobody/Anonymous (nobody) Summary: Quick reply generation Initial Comment: In network protocols, messages are often confirmed by the receiver. In order to model such protocols effectively, it would be nice to define a set of replies (either with constant text or a using some sort of patterns), assign them to some shortcuts (which can ideally be fired just by left hand) and then, when a message is selected and a shortcut is pressed, the defined reply would be generated right after the selected message, having the selection changed to this generated reply. The function should also be accessible via the SCStudio menu. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046489&aid=3436280&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-11 00:33:07
|
Feature Requests item #3436277, was opened at 2011-11-10 16:33 Message generated for change (Tracker Item Submitted) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046489&aid=3436277&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open Priority: 3 Private: No Submitted By: Ondřej Bouda (obouda) Assigned to: Nobody/Anonymous (nobody) Summary: Batch page insert Initial Comment: Since the instances are often the same within a single document, it would be nice to insert new pages more effectively than manually inserting a page, renaming it and pasting a previously copied common shapes, ideally at the same position. One would like to tell SCStudio: "These are shapes common to all pages. Create pages containing the current selection (or all shapes on the page if nothing is selected), the first named X, the second named Y, ..." ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046489&aid=3436277&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-11 00:24:02
|
Bugs item #3436273, was opened at 2011-11-10 16:23 Message generated for change (Tracker Item Submitted) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3436273&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ondřej Bouda (obouda) Assigned to: Martin Bezděka (mbezdeka) Summary: Connection points persist on copied instances Initial Comment: When copying an instance, which has some events (i.e. messages) bound to it, the copied instance also contains these connection points, even though the corresponding messages were not copied. Connection points should be removed from the copied instance after copying (either via Ctrl+drag&drop or copy&paste) if the corresponding connected objects are not also copied. The bug might also apply to other shapes, not just instances. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3436273&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-09 19:16:23
|
Bugs item #3435701, was opened at 2011-11-09 11:16 Message generated for change (Tracker Item Submitted) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3435701&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ondřej Bouda (obouda) Assigned to: Martin Bezděka (mbezdeka) Summary: Context menu not available for all pages except the first Initial Comment: The SCStudio context menu for the paper (containing items such as Add Instances, Message Numbering, etc.) is only available on the first page of the drawing. On other pages the menu is not there (both right after creating that page, and after loading an existing document). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3435701&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-09 19:13:27
|
Bugs item #3435698, was opened at 2011-11-09 11:13 Message generated for change (Tracker Item Submitted) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3435698&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ondřej Bouda (obouda) Assigned to: Martin Bezděka (mbezdeka) Summary: Add Instances: default focus on number of instances input Initial Comment: When the Add Instances dialog appears, the input for number of instances should have focus for the user to immediately enter it. Currently, the default focus is on the OK button. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3435698&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-09 19:11:26
|
Feature Requests item #3435697, was opened at 2011-11-09 11:11 Message generated for change (Tracker Item Submitted) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046489&aid=3435697&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open Priority: 5 Private: No Submitted By: Ondřej Bouda (obouda) Assigned to: Nobody/Anonymous (nobody) Summary: Add Instances: total width specification using mouse Initial Comment: The Add Instances function shows a dialog which allows the user to specify the total width, which the generated messages must fit in. The width is entered as a number, though. Specifying the total width using a mouse would be better. After confirming the dialog with number of instances to generate, the user would drag a box (just like a selection) inside which the messages would be placed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046489&aid=3435697&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-09 19:05:39
|
Feature Requests item #3435695, was opened at 2011-11-09 11:05 Message generated for change (Tracker Item Submitted) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046489&aid=3435695&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open Priority: 5 Private: No Submitted By: Ondřej Bouda (obouda) Assigned to: Nobody/Anonymous (nobody) Summary: Keyboard shortcuts for dropping messages Initial Comment: Dragging messages from the shapes panel is really a slow way of drawing diagrams. It would be nice to have a keyboard shortcut for dropping a message exactly to the position of cursor. (Thanks to message autosnapping, it usually gets connected to required instances.) Define two keyboard shortcuts, one for each direction (left-to-right, right-to-left). The user should be able to invoke the shortcut just by their left hand (because they hold mouse in right hand, mostly, which specifies the location to drop the message). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046489&aid=3435695&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-09 18:53:35
|
Bugs item #3199693, was opened at 2011-03-04 07:08 Message generated for change (Comment added) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3199693&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open Resolution: None Priority: 9 Private: No Submitted By: Radek Sedláček (rsedlac) Assigned to: Martin Bezděka (mbezdeka) Summary: Changing the length of instances - configuration Initial Comment: It must be configurable whether messages connected to instances 1. move proportionally as the instances are being prolonged/shortened or 2. they keep their position. In both cases the messages must remain connected. ---------------------------------------------------------------------- Comment By: Ondřej Bouda (obouda) Date: 2011-11-09 10:53 Message: Even if configuration is not needed, the behaviour should be consistent. Currently, in some cases, it happens that a message end point (message send or receive event) is anchored to the bottom of the corresponding instance, while other message events are (correctly) anchored to instance heads. See the attached examples: - Bluetooth-sample.vsd - Bad-anchors2.vsd - Bad-anchors3.vsd (here, the last message receive event is anchored to the bottom, but after adding another message underneath it between the same instances in the same directions, both messages are anchored incorrectly, whereas adding that message in the opposite direction implies bad anchoring only of this lastly added message and the previous is suddenly OK) - Bad-anchors4.vsd - example of message send event anchored incorrectly Either way, after reattaching the messages to the instances by hand, even in exactly the same point on the instance, they get anchored to the instance head (as expected). ---------------------------------------------------------------------- Comment By: Radek Sedláček (rsedlac) Date: 2011-05-18 00:26 Message: Configuration is not needed. Automatically connected messages shall keep their position when the instances are being prolonged/shortened. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3199693&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-09 18:39:44
|
Bugs item #3367416, was opened at 2011-07-14 10:20 Message generated for change (Comment added) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3367416&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: Martin Bezděka (mbezdeka) Assigned to: Nobody/Anonymous (nobody) Summary: Loading scstudio takes too much time Initial Comment: Probably caused by help folder. ---------------------------------------------------------------------- Comment By: Ondřej Bouda (obouda) Date: 2011-11-09 10:39 Message: Some year ago, loading was OK, the problems appeared after a concrete commit to the Visio interface. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3367416&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-09 18:36:29
|
Feature Requests item #3435684, was opened at 2011-11-09 10:36 Message generated for change (Tracker Item Submitted) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046489&aid=3435684&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open Priority: 5 Private: No Submitted By: Ondřej Bouda (obouda) Assigned to: Nobody/Anonymous (nobody) Summary: Expression separator autosnapping Initial Comment: Similarly to messages, it would be nice if the expression separator snapped automatically to the borders of the inner-most inline expression, when dropped inside it. Secondly, the expression separator should be bound to the inline expression even when the inline expression box gets resized. Currently, the expression separator keeps its dimensions regardless any dimension changes of the corresponding inline expression. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046489&aid=3435684&group_id=219467 |
|
From: SourceForge.net <no...@so...> - 2011-11-09 18:29:40
|
Feature Requests item #3435676, was opened at 2011-11-09 10:28 Message generated for change (Settings changed) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046489&aid=3435676&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Visio Interface Group: None Status: Open >Priority: 3 Private: No Submitted By: Ondřej Bouda (obouda) Assigned to: Nobody/Anonymous (nobody) >Summary: Don't stretch Comments and Texts automatically in Visio Initial Comment: Currently, when a comment or text box is stretched horizontally in one direction, it stretches symmetrically in the other direction as well. That is quite awkward, no automatic symmetric stretching should take place for the user to position the comment (or text) box just as expected. The goal of this task (rather an improvement than a feature request) is to disallow such automatic symmetric stretching. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046489&aid=3435676&group_id=219467 |
