startpoint | Start Point For Creating Apps | Ecommerce library

Instead of using isPresented for .sheet you can use .sheet(item:, content:) and pass the whole result object

from the template you can access to it from $route object like $route.query and from the vue instance you can write this.$route.query

also you can check the $route object from vue dev tools. check out the picture below:

to pass the queries to data object you can just write:

Ok I found by myserlf, here is the solution if someone else need :

1. Do you have only one item in your ComboBox? The built-in behavior of a ComboBox after an item is selected is to collapse. Selecting an element is the transfer of focus, including to any of its child elements. As soon as you click on the Slider it receives focus, the item is selected and the CombobBox collapses.

2. In general, it looks like some kind of nonsense, complete . ComboBox is for selecting items from a list of items that you don't even have. If you just need to hide-reveal a set of elements, then use Expander.

3. If you need something different, then explain normally and in detail what you want to implement.

The answer is supplemented by an explanation for additional details in the question:

I'm trying to make a context menu where I can move the slider and so that it doesn't close, the expander doesn't fit because I don't need to move the elements of my window, but open on top of it

In WPF, elements are selected based on their behavior logic. And their visual appearance is set by styles and/or templates.
ComboBox behavior: when you click on it, expand the list, when you click on an item in the list, select it and collapse the list.

Do you need this behavior?
Not.
Hence you don't need a ComboBox.

Most likely, judging by your description, you need a combination of ToggleButton and Popup.

A simple example:

Notice in the working example you have a transparent brush set to the Stroke property.
But in the first example, nothing is set to this property.
Hence it is null.
And null has no properties to animate them.

You can explicitly set SolidColorBrush instance in this property, give this instance a name, and access its Color property directly.
It will be much easier than all these casts.

Example:

I think your best bet is to "mask" the gradient, rather than trying to calculate the endPoint.

Here's an example with 5 "bars" in an HStack - the first bar has a max value of 10, then the bars' values go 9, 7.5, 5, 2:

Sample code:

You can use /*:map/*:string[@key = 'url'] or declare the fn namespace (with e.g. xmlns:fn="http://www.w3.org/2005/xpath-functions") and use it instead of the wildcard with e.g. /fn:map/fn:string[@key = 'url'].

Or upwards with e.g. ../../fn:string[@key = 'url'].

What a fun problem :)

The "naive" approach would be to render the gradient as a square and then either rotate it or squeeze or stretch it to fit the rectangle. Rotating requires more maths so here's the "squeezing" version: