Closed ruvater closed 9 years ago
Don't worry, it's "normal". The #123 PR will fix this when @jeremyletang will merge it.
Actually that's not the same errors, @jeremyletang has fixed them. It will create a PR for it.
hey @ruvater, can you try to with the last commit ? The problem should be fix now.
@jeremyletang so... those errors was fixed, but unfortunately there are fresh ones:
bob@bob-laptop:~/Programming/calc$ cargo run
Compiling rgtk v0.0.1 (https://github.com/jeremyletang/rgtk.git#9f1d1550)
src/gtk/widgets/value.rs:110:54: 110:60 error: mismatched types: expected `i32`, found `i64` (expected i32, found i64)
src/gtk/widgets/value.rs:110 unsafe { ffi::g_value_set_long(self.pointer, v_long) }
^~~~~~
src/gtk/widgets/value.rs:114:18: 114:53 error: mismatched types: expected `i64`, found `i32` (expected i64, found i32)
src/gtk/widgets/value.rs:114 unsafe { ffi::g_value_get_long(self.pointer) }
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/gtk/widgets/value.rs:118:55: 118:62 error: mismatched types: expected `u32`, found `u64` (expected u32, found u64)
src/gtk/widgets/value.rs:118 unsafe { ffi::g_value_set_ulong(self.pointer, v_ulong) }
^~~~~~~
src/gtk/widgets/value.rs:122:18: 122:54 error: mismatched types: expected `u64`, found `u32` (expected u64, found u32)
src/gtk/widgets/value.rs:122 unsafe { ffi::g_value_get_ulong(self.pointer) }
I'm not that good at Rust, but I could try to fix it tonight.
hey @ruvater,
This have probably been introduced by the PR from @GuillaumeGomez. The last commit should fix this. Tell me if you have more bug like this, @GuillaumeGomez and me both work on 64bit computer, so we may have some "cast" problem for long value.
@jeremyletang
Great, guys. Thanks! It works fine now.
It's kinda obvious what to do with the first error, but I haven't got a clue about the others.