Why doesn't CE View allow you to 'Copy to Clipboard'? The previous versions did, but the new one doesn't. This is a feature that I used a lot.
I have noted that this was previously discussed by yourself a while ago which resulted in Defect # 354633. This defect has been looked at by our development team and deemed to be Working As Designed. Bentley View is a viewer and not something a user should expect to be performing a Copy&Paste within.
Regards Andrew Bell
Andrew Bell said:Bentley View is a viewer and not something a user should expect to be performing a Copy&Paste within.
despite of I am not using clipboard copy/paste in Bentley products too often, I strongly disagree with the decision and such justification. To remove already implemented feature from a product, especially when it existed in the past, just makes the product worse and UX worse ... and user more dissapointed, which is something that unfortunately CONNECT Edition from its release is about.
I think clipboard support is not required for "certified for Windows" by Microsoft, but it's expected any Windows application supports it and as Mark noted, viewing software like Adobe Reader supports it ... and it's not only Reader, which makes the justification void.
I can imagine a lot of workflows and situations where to use "copy from View" makes sense. It's not about how Stuart use it, but e.g. when documents are created, to copy graphics inside them is big help. Do you recommend to use complete MicroStation to do it? To capture picture is not alwyas proper solution.
Labyrinth Technology | dev.notes() | cad.point
Dan Eng said:As a viewing application, we only allow viewing of the file and do not allow you to copy the elements to the clipboard and then paste them into a authoring application.
with all respect, I totally disagree with your explanation. I am not able to find any logic in the justification: Bentley View is viewing application, so the most of (maybe 99%?) of installations is on computers where there is no "authoring application". But you explain a lack of functionality using Stuart's workflow, which is, in the context of View users, probably very rare. Such explanation is more a tergiversation, especially when the functionality existed in the past ... and probably all other vieweing applications, regardless CAD or common office apps, offer it as a standard functionality.
Dan Eng said:This would minimize any potential issues of something going incorrectly when copying to the clipboard outside of MicroStation and then back into the DGN
Maybe it would be more efficient to design and implement copy tool in a professional way and at similar level as competitive products offer it? I have been working with Bentley products for nearly 30 years, doing literally everything from support and sales to development and on-site consultancy and customatization, and inability to efficiently copy an element from one file to another has been discussed ... hmmm ... all this time?
I think Stuart uses the described workflow and the clipboard because he wants to use View in not standard way, but it's "simply to be used" workaround, because Bentley do not offer proper functionality in core product.
Dan Eng said:This would minimize any potential issues of something going incorrectly when copying to the clipboard outside of MicroStation and then back into the DGN, I suggest you reference the file into your DGN and then use the MicroStation Copy tools.
Do you use MicroStation on some real project? There is a model with plenty of (tens and hundreds) nested references, thousand of levels, so when a reference will be attached (again with many references and levels), you have to change MicroStation setting (probably open a new view, switch off unwanted levels, find the element in complex model...) to navigate to the element and be able to copy it somehow, which sometimes will require to break MicroStation setting, workflows or MicroStation customization (Global Display...).
Instead of very vague formulation, can you provide exact step by step description how to do it using reference, on real project? I have discussed it with my customers several times in the past and we always ended with at least several not very simple and intuitive steps. So maby be your recommendation is valid and better, because a shortcut exists and I have overlooked it.
Dan Eng said:then please create an Idea and we can evaluate it.
I like Ideas a lot, but unfortunately it has become universal solution for Bentley when original design of a feature and its implementation is not done properly.
I am aware I am hijacking the discussion a bit, but let's make a research how MicroStation Ideas looks today:
As one from my customer and my friend told me, when I recommended him to post an Idea: "I will wrote the ideas and my complains on papers and will throw them out of the windows. An effect and output will be the same, but it will be more fun."
My formulation is that it should be win-win, but it's win-lost. As stuartw wrote in other discussion about commenting blogs: When Bentley colleague creates a blog, he is obligued to answer consequent questions in forum. It's not usually happening. I would apply the same rule to Ideas: When Bentley asked users to invest their time to formulate Ideas, add images or videos and other users comment them, Bentley should be obligued to don't use Ideas as a trash, but to keep the Ideas living and to provide consistent feedback how Ideas are processed.
Because it's not happening, I understand that some users dislike Ideas and treat them as useless and lost time.
My impression is also that no-one at Bentley ever works on real projects as then lots of flaws and bugs would become apparent right away and could get rid of before release time.
Hi Jan and Stuart,
Thank you for bringing the workflows and scenario to our attention and the use case for Bentley View CONNECT Edition. I'll discuss this with the team to see how we may enhance it in the future.
Dan Eng said:I'll discuss this with the team to see how we may enhance it in the future
Why do you consider it an enhancement to provide clipboard copy in Bentley View CONNECT, when it was an existing capability of previous versions? From the customer's point of view, it's not an enhancement request. It's a plea to maintain the same functionality as before.
Regards, Jon Summers LA Solutions
I used the term "enhance" in a sense that we will see what we can do to change and include this in a future update. We can call it a defect. In the meantime, I'll get with the team to discuss this to see about bringing this back in.
Defect 1004801 has been filed on this.
Dan Eng said:Defect 1004801 has been filed on this.
Thanks I think but still don't understand why it was removed.
Also why is this Update 11 when this is only the second release of CE View?
stuartw said:Also why is this Update 11 when this is only the second release of CE View?
my interpretation why it's Update 11 and why I think it's logical: Bentley View can be seen as cut/limited version of MicroStation. Technically both are based on Power Platform (as well as all other products like ORD etc.). Because there is no extra industry specific functionality, it makes sense (at least to me ;-) to use the same naming as for MicroStation.
So my assumption is that Bentley View CE Update 11 is based on the same Power platform (engine) version as MicroStation CE Update 11.
Jan is correct. We kept the Update 11 in Bentley View CONNECT Edition since it is based on the Update 11 PowerPlatform. Since we will be rolling out regular updates of Bentley View CONNECT Edition, we wanted to keep it consistent with MicroStation CONNECT Edition and PowerDraft CONNECT Edition releases.