readme out of date

[n1ght-hunter]

Is there an existing issue for this?

• I have searched the existing issues.

Is this issue related to iced?

• My hardware is compatible and my graphics drivers are up-to-date.

What happened?

the readmes are out of date
version is wrong
https://github.com/iced-rs/iced/blob/ee105e3bee1bc676dcf3324693984ccda8e4e733/core/README.md

What is the expected behavior?

NA

Version

master

Operating System

Windows

Do you have any log output?

No response

[ccpwcn]

When I saw #2346, I thought the problem was fixed. So...

I'm imported iced 0.12.1, copied code from https://github.com/iced-rs/iced/blob/master/examples/counter/src/main.rs
It really sucks, The bug still exists.

//隐藏Windows上的控制台窗口
#![windows_subsystem = "windows"]

use iced::widget::{button, column, text, Column};
use iced::Alignment;

pub fn main() -> iced::Result {
    iced::run("A cool counter", Counter::update, Counter::view)
}

#[derive(Default)]
struct Counter {
    value: i64,
}

#[derive(Debug, Clone, Copy)]
enum Message {
    Increment,
    Decrement,
}

impl Counter {
    fn update(&mut self, message: Message) {
        match message {
            Message::Increment => {
                self.value += 1;
            }
            Message::Decrement => {
                self.value -= 1;
            }
        }
    }

    fn view(&self) -> Column<Message> {
        column![
            button("Increment").on_press(Message::Increment),
            text(self.value).size(50),
            button("Decrement").on_press(Message::Decrement)
        ]
        .padding(20)
        .align_items(Alignment::Center)
    }
}

cargo run

[ccpwcn]

iced = "0.12" doesn't work either.

[ccpwcn]

iced = "0.12.0" doesn't work either.
iced = "0.10.0" doesn't work either.
iced = "0.0.0" doesn't work either.

All of them, cannot find the iced::run function. But I saw this function in 0.13.0-dev.

[hecrj]

[alex-ds13]

Actually this issue is related to the iced_core README file that still tells to use version 0.9 even on master branch.

The comments from @ccpwcn are unrelated to this issue itself. Was wrongfully directed here from issue #2346 which is actually the problem they're facing. I've already responded there.

[alex-ds13]

The same thing happens on the iced_wgpu README.

But since I don't think there is many people using the iced_core or iced_wgpu crates directly I don't think this is that much of an issue...