This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
1) Ability to specify interface(s) that an entity need to implement 2) Have the entity implements the interface when using the refactor tool to extract interface 3) Right click on the LightSpeed Model window and get the same kind of right click menu as in Designer That's all, many thanks!! :)
|
|
|
4) Display and group by Namespace in the LightSpeed Model window 5) If a procedure is linked to an entity, why not have a Procedures folder under each entity in the LightSpeed Model window? 6) The Add menu items in the LightSpeed Model window seems to be a bit odd, only available when click on the root node? |
|
|
(1) You can already do this in the partial class: partial class Spline : IReticulable { } What do you see as the benefit to being able to do it in the designer as well? (2) Again, if you declare the interface in the partial class, you can have VS create a stub implementation using Ctrl+.. (3) Interesting idea! We would have to think about the behaviour for nonvisual items but it could save us a lot of writing "Open the LightSpeed Model Explorer" in support posts! Thanks for the suggestion! (4) Do you mean a by-namespace filter option (like the by-tag filter) or do you mean organising the entities into by-namespace folders in the tree? The first we can do, the second we won't unless there is a lot of demand for it (for reasons explained in (5)). (5) The folder structure is generated by Visual Studio and represents the underlying structure of the lsmodel file. Modifying the folder structure is a lot of effort, and we have to prioritise. Sorry. (6) Again, the menu is generated by Visual Studio and is very hard for us to modify. We agree it's badly designed, but we don't feel we can justify the effort to try to fix it. |
|
|
Hi Ivan, Thank you so much for responding to my suggestions! :) (1) I'm after the ability to visually select a number of entities and set their interface to IReticulable. In addition, it would be nice to see which entity implement which interface without digging into the partial classes. I guess I'm looking for an experience that doesn't require me to jump between editor and designer. (3) :) (4) It can be as simple as displaying each item as displaying [Namespace].[Entity] instead of just [Entity] and sort the list by [Namespace] and [Entity] (5) OK (6) OK Many thanks! Joseph |
|