Build 1703 „Find Command“ is missed

[PeterHeintz]

In build 1703 the „Find Command“ feature is missed (as I assume by mistake).

[Eve]

As was the case before 17, it's limited to some visual styles.

[PeterHeintz]

Ok, I found it in Style Office 2016.
But I think you can admit this is quiet tricky.

[Geert Bellekens]

The tricky part is that installing the new version also changed my preferred visual style to one where the find command is not available.

Geert

[BobM]

Ok, I found it in Style Office 2016.
But I think you can admit this is quiet tricky.

In office 2016 its on top,
in all other user interface versions its in the EA menu

[Geert Bellekens]

That is almost (but not 100%) the same search box.

There is small differences in behavior and results between the two.

Geert

[BobM]

That is almost (but not 100%) the same search box.

There is small differences in behavior and results between the two.

Geert

I'm sceptical sparx devs would code specific behavior for one single visual style, but I'll bite; Can you give examples of small differences where the box would be lacking functionality over the office 2016 visual style box (or vice versa)?

[Geert Bellekens]

That is almost (but not 100%) the same search box.

There is small differences in behavior and results between the two.

Geert

I'm sceptical sparx devs would code specific behavior for one single visual style, but I'll bite; Can you give examples of small differences where the box would be lacking functionality over the office 2016 visual style box (or vice versa)?

If you type in "trace" you get different results.
I don't know if that proves Sparx devs wrote different code, but the end result is that there are small differences.



Geert

[PeterHeintz]

Anyhow it is a "confuse the users" feature!

[Takeshi K]

Just for your information, the Ribbon (and the whole window management) is implemented using a third party library. We can know this by using some tools (e.g. Spy++).

So I would say that all the behaviour related to the Ribbon is defined outside the Sparx developers. You may say that they should change the behaviour, but I think they should concentrate on their own code and it is a nice solution to buy 'existing' features, even if they are not perfect for all of us.

You might also say that they should choose the 'perfect' library for everyone and every situation, not just at the time of selection, but in the future. I agree, if that is possible.

[qwerty]

In Germany we say that "the fish stinks from its head". Looking back, most of the EAUI is caused by Mickeysoft's weirdness. Another saying: "The apple does not fall far from the tree trunk" probably applies in consequence.

q.

[PeterHeintz]

I do not say to what Sprax should concentrate anyway!
I just say it is confunsing!😉