Hello Michaël,
On 06/22/2012 11:52 PM, Michaël Bouchaud wrote:
My mind isn't fixed, look svn ^^
but if you can provide a better example, I take it ! :)
Your patch go in, thx !
cool, thanks. I have attached a patch with an example for the changed
signal. I hope this makes sense. I also
On 06/21/2012 11:34 PM, Michaël Bouchaud wrote:
Sorry, but I really cannot identify your use case. The only utility
that I see to emit a changed signal is to be noticed that the
progressbar value has changed ... But we will not use the value
later, but surely not to redefine a new format.
My mind isn't fixed, look svn ^^
but if you can provide a better example, I take it ! :)
Your patch go in, thx !
2012/6/22 Daniel Willmann d.willm...@samsung.com
On 06/21/2012 11:34 PM, Michaël Bouchaud wrote:
Sorry, but I really cannot identify your use case. The only utility
that I see to
Sorry, but I really cannot identify your use case. The only utility that I
see to emit a changed signal is to be noticed that the progressbar value
has changed ... But we will not use the value later, but surely not to
redefine a new format. format_func is here to do that.
2012/6/20 Daniel
Hello,
On 06/19/2012 11:57 PM, Michaël Bouchaud wrote:
Damn !!!
sorry raster, I've forget to send my draft answer.
I have talked to the author on irc, but I don't warned you to not apply
it
just to clarify, raster asked me about the patch on irc and I told him
that you already applied a
On Thu, 14 Jun 2012 15:04:40 +0100 Daniel Willmann d.willm...@samsung.com
said:
thanks! in svn it is!
Some more discussion in IRC led to the conclusion that this should be a
handled in a signal callback I've attached the new patch where I also
updated the progress bar example.
--
Damn !!!
sorry raster, I've forget to send my draft answer.
I have talked to the author on irc, but I don't warned you to not apply
it
I've rewrited this patch in a diffferent way and it's already commited.
Sorry for your waste of time to review it... but I must revert it.
Sorry sorry sorry,
On 06/14/2012 12:15 AM, Michaël Bouchaud wrote:
Hum not really needed as is...
We just need a format function here ...
a progressbar is from 0.0 to 1.0.
Some more discussion in IRC led to the conclusion that this should be a
handled in a signal callback I've attached the new patch where I
Hum not really needed as is...
We just need a format function here ...
a progressbar is from 0.0 to 1.0.
2012/6/12 Daniel Willmann d.willm...@samsung.com
Hello,
updated version. I added the @since 1.1 mentioned by Stefan and
mentioned the default value.
Regards,
Daniel
These functions
These functions change the range of the value displayed on the progress
bar with elm_progressbar_unit_format_set. At the moment the value displayed
is in the range of 0 to 100. These functions allow you to change the upper
range to something else.
This is useful if the value represented by the
Hello.
On 06/12/2012 11:24 AM, Daniel Willmann wrote:
/**
+ * Set the range of the value displayed on a given progress bar
+ * widget
+ *
+ * @param obj The progress bar object
+ * @param scalemax The maximum value
+ *
+ * This sets the range of the value that is displayed on a progress
Hi, Daniel.
+ return sd-maxunit;
+}
+
+EAPI void
elm_progressbar_span_size_set(Evas_Object *obj,
Evas_Coord size)
{
diff --git a/trunk/elementary/src/lib/elm_progressbar.h
b/trunk/elementary/src/lib/elm_progressbar.h
index 5ee2aff..49ee65a 100644
---
Hello,
updated version. I added the @since 1.1 mentioned by Stefan and
mentioned the default value.
Regards,
Daniel
These functions change the range of the value displayed on the progress
bar with elm_progressbar_unit_format_set. At the moment the value displayed
is in the range of 0 to 100.
13 matches
Mail list logo
