[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4668: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3815)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4670: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3815)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4671: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3815)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4672: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3815)
XWidgetSoft Forum :: View topic - HELP: Opacity expressed differently in code vs IDE - CLOSED
XWidgetSoft Forum
https://bbs.xwidget.com/

HELP: Opacity expressed differently in code vs IDE - CLOSED
https://bbs.xwidget.com/viewtopic.php?f=8&t=6350		 Page 1 of 1
Author:  yereverluvinuncleber [ June 4th, 2016, 2:24 pm ]
Post subject:  HELP: Opacity expressed differently in code vs IDE - CLOSED
In the IDE the opacity of an object can be expressed from 1-100 in percentage terms. That is good.

However, in the use of code there is a massive inconsistency, the object's opacity can only be set at two values, either 0 or 1. Transparent or opaque.

It is as if Tony has forgotten that opacity is different from visibility. Visibility is correctly expressed as a boolean whilst opacity is a gradient from 1-100 or 0-255.

Most other engines and languages will allow opacity to be expressed in values from 0-255. The Xwidget IDE having only a percentage available is limited but just acceptable but the code limitation of an opacity limited to 0 or 1 is unacceptable. This, without a doubt - is a BUG.
Author:  Jimking [ June 4th, 2016, 3:40 pm ]
Post subject:  Re: BUG: Opacity is expressed differently in code vs IDE
I know what do you mean and if through the js doesn't work properly I agree that something is wrong. But I have the same question: When you want a certain function that you can simply use through the designer's menu, why you try to do all through the script..?! There is already the opacity meter for all the components and works perfectly! Why don't use it..? I will never understand you on this.... :lol:

I can understand that as a prof designer you are used to do it, but I checked all your widgets and none of them uses neither one of the designer's functions.. This is crazy man..! :?

(friendly speaking of course, so don't take my comment as an accusation. You're free to do it as you want)
Author:  yereverluvinuncleber [ June 4th, 2016, 5:49 pm ]
Post subject:  Re: BUG: Opacity is expressed differently in code vs IDE
No, you have it all wrong. I am changing the opacity in code because I have a function that simply requires it. Changing it in the IDE is not relevant to this function so it has to be done in code. The function that I am coding no longer operates when I tried to implement it because of the inconsistency in xwidget's handling of opacity in scripts.
Author:  Jimking [ June 4th, 2016, 6:21 pm ]
Post subject:  Re: BUG: Opacity is expressed differently in code vs IDE
You know better. It's your work after all. I will see it in practice then..
Author:  yereverluvinuncleber [ June 4th, 2016, 6:53 pm ]
Post subject:  Re: BUG: Opacity is expressed differently in code vs IDE
Go to bed!
Author:  meme [ June 4th, 2016, 10:15 pm ]
Post subject:  Re: BUG: Opacity is expressed differently in code vs IDE
Try
edit1sensor1.Opacity = 0.5
The range appears to be 0 to 1
Seems to work for me.
Author:  yereverluvinuncleber [ June 5th, 2016, 3:58 am ]
Post subject:  Re: BUG: Opacity is expressed differently in code vs IDE
Wow, the instructions expressed an int boolean - I'll check and see, thankyou!
Author:  yereverluvinuncleber [ June 5th, 2016, 7:24 am ]
Post subject:  Re: BUG: Opacity is expressed differently in code vs IDE
Meme, your suggestion worked - perfectly.

To have a percentage expressed as a decimal value below 1 is quite bizarre when the IDE expresses it as you would expect as an integer value between 1 and 100. Other engines express it as a value from 0-255 but base javascript does express it in the same way as Xwidgets. I suppose I should have guessed it but what led me astray is that the auto-completion suggest is purely an integer value of either 0 or 1 (I won't trust that anymore).

Thanks again.
Page 1 of 1 All times are UTC - 8 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/