You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My hardware is compatible and my graphics drivers are up-to-date.
What happened?
When running the application on Windows 10 Pro 64 bits I get the following behavior, a prompt window opens for a few seconds, and then it closes, as shown in the video below
WhatsApp.Video.2024-04-01.at.11.51.32.PM.mp4
My development environment
Compiled using cargo build --release --target x86_64-pc-windows-gnu
My Cargo.toml
[package]
name = "costv"version = "0.1.0"edition = "2021"# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[dependencies]
iced = { version = "0.12.1", features = ["lazy"] }
iced_core = "0.12.3"
[profile.release]
strip = true
What is the expected behavior?
This is the expected behavior
Version
crates.io release
Operating System
Windows
Do you have any log output?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Is this issue related to iced?
What happened?
When running the application on Windows 10 Pro 64 bits I get the following behavior, a prompt window opens for a few seconds, and then it closes, as shown in the video below
WhatsApp.Video.2024-04-01.at.11.51.32.PM.mp4
My development environment
![Screenshot 2024-04-02 22 04 56](./?url=aHR0cHM6Ly9wcml2YXRlLXVzZXItaW1hZ2VzLmdpdGh1YnVzZXJjb250ZW50LmNvbS8xNDg1NDg5MS8zMTkwMDUxMDktMDc0ZGNhNmYtYTMwYi00ZmRhLWIwMjUtOGI3ZTBjNmIwMDc3LnBuZz9qd3Q9ZXlKaGJHY2lPaUpJVXpJMU5pSXNJblI1Y0NJNklrcFhWQ0o5LmV5SnBjM01pT2lKbmFYUm9kV0l1WTI5dElpd2lZWFZrSWpvaWNtRjNMbWRwZEdoMVluVnpaWEpqYjI1MFpXNTBMbU52YlNJc0ltdGxlU0k2SW10bGVUVWlMQ0psZUhBaU9qRTNNalF3TkRBM09EQXNJbTVpWmlJNk1UY3lOREEwTURRNE1Dd2ljR0YwYUNJNklpOHhORGcxTkRnNU1TOHpNVGt3TURVeE1Ea3RNRGMwWkdOaE5tWXRZVE13WWkwMFptUmhMV0l3TWpVdE9HSTNaVEJqTm1Jd01EYzNMbkJ1Wno5WUxVRnRlaTFCYkdkdmNtbDBhRzA5UVZkVE5DMUlUVUZETFZOSVFUSTFOaVpZTFVGdGVpMURjbVZrWlc1MGFXRnNQVUZMU1VGV1EwOUVXVXhUUVRVelVGRkxORnBCSlRKR01qQXlOREE0TVRrbE1rWjFjeTFsWVhOMExURWxNa1p6TXlVeVJtRjNjelJmY21WeGRXVnpkQ1pZTFVGdGVpMUVZWFJsUFRJd01qUXdPREU1VkRBME1EZ3dNRm9tV0MxQmJYb3RSWGh3YVhKbGN6MHpNREFtV0MxQmJYb3RVMmxuYm1GMGRYSmxQV00zTkdJeFlXWmxaREl5TVRReVpqTTNOR0kzWWpVNFpUTTJZMlprWVdNNFptTTJPVFJtWWpGbE1tSmlaak13Wkdaa05UZzBNalUwT1RNNVpEUTBaVEFtV0MxQmJYb3RVMmxuYm1Wa1NHVmhaR1Z5Y3oxb2IzTjBKbUZqZEc5eVgybGtQVEFtYTJWNVgybGtQVEFtY21Wd2IxOXBaRDB3SW4wLlJuSzkyLV8yRTU0ajZreE50QXVXOTZ4ajEwV0hNcDhjZEp0bXFnV0pjUzA=&__proxy_form=0)
Compiled using
cargo build --release --target x86_64-pc-windows-gnu
My Cargo.toml
What is the expected behavior?
This is the expected behavior
![Screenshot 2024-04-02 21 57 56](./?url=aHR0cHM6Ly9wcml2YXRlLXVzZXItaW1hZ2VzLmdpdGh1YnVzZXJjb250ZW50LmNvbS8xNDg1NDg5MS8zMTkwMDU1NjEtMzlhMjU1MDUtMjM2MS00MDFmLTgzMzEtN2EzNWY3MDczNzM2LnBuZz9qd3Q9ZXlKaGJHY2lPaUpJVXpJMU5pSXNJblI1Y0NJNklrcFhWQ0o5LmV5SnBjM01pT2lKbmFYUm9kV0l1WTI5dElpd2lZWFZrSWpvaWNtRjNMbWRwZEdoMVluVnpaWEpqYjI1MFpXNTBMbU52YlNJc0ltdGxlU0k2SW10bGVUVWlMQ0psZUhBaU9qRTNNalF3TkRBM09EQXNJbTVpWmlJNk1UY3lOREEwTURRNE1Dd2ljR0YwYUNJNklpOHhORGcxTkRnNU1TOHpNVGt3TURVMU5qRXRNemxoTWpVMU1EVXRNak0yTVMwME1ERm1MVGd6TXpFdE4yRXpOV1kzTURjek56TTJMbkJ1Wno5WUxVRnRlaTFCYkdkdmNtbDBhRzA5UVZkVE5DMUlUVUZETFZOSVFUSTFOaVpZTFVGdGVpMURjbVZrWlc1MGFXRnNQVUZMU1VGV1EwOUVXVXhUUVRVelVGRkxORnBCSlRKR01qQXlOREE0TVRrbE1rWjFjeTFsWVhOMExURWxNa1p6TXlVeVJtRjNjelJmY21WeGRXVnpkQ1pZTFVGdGVpMUVZWFJsUFRJd01qUXdPREU1VkRBME1EZ3dNRm9tV0MxQmJYb3RSWGh3YVhKbGN6MHpNREFtV0MxQmJYb3RVMmxuYm1GMGRYSmxQVFkwTnpaall6azFNamhtTVRBNE1tSXlZbVkwWVRsaE16VmpNREF6WW1FeU56SmtORFZoTWpsbE5UaGtZamsyT1RnNE9EYzJaVGcyWkRka1l6UXpZVE1tV0MxQmJYb3RVMmxuYm1Wa1NHVmhaR1Z5Y3oxb2IzTjBKbUZqZEc5eVgybGtQVEFtYTJWNVgybGtQVEFtY21Wd2IxOXBaRDB3SW4wLl9ZQ3JDS0JhX3hQR0pBOERvLUtnc1E1eGNiTHNMMXlQZ0dZdXJYd3NaNGc=&__proxy_form=0)
Version
crates.io release
Operating System
Windows
Do you have any log output?
No response
The text was updated successfully, but these errors were encountered: