Hi developers, I want to know whether, Webvisu is open source? Can anyone interested in development contribution having knowledge of web based development join and contribute? Regards Nadim
A small amendment to my previous statement: The abnormal behaviour is relatied to the type of variable If INTEGERS are going to be displayed the problem occurs , with REAL display in correct Looks like if integers are misintepreted perhaps
Histogram Glitches
Dynamic image change through variable bitmap
Hi Frank Thank you very much for taking your time to answer our question, we really appreciate this. We spent some time yesterday and figured out the drawing part of it as well. Regarding your question, the expr-*-color - that always reference variables, are used when one adds variable names to this dialog in CoDeSys Element Configuration - Colorvariables: We only implemented the "Fill Color" variable for now, as this currently suffices. The parsing code used (codesys.pp.js, inserted at line 742),...
Hi vali dan, Thank you for your efforts to contribute a solution to the problem you found. Unfortunately it is not that easy to implement. The parsing is only the first half; the continuous evaluation of the variable and the drawing is the other half. First of all: when can such an expression be specified? How can we determine wether we should use the constant "fill-color" or the expression "expr-fill-color"? Then we have to pass the expression "expr-fill-color" and probably also "expr-fill-color-alarm"...
I currently have no running system here, but I guess this should be the way: var exprFillColor = []; var expr_fillColor = $myMedia.find('expr-fill-color'); if (expr_fillColor.length) { exprFillColor = parseExpression(expr_fillColor); // get value from visuVariables // name is e.g. ".dwFarbe_F1" - value e.g. "4,418284,4,5" exprFillColorRAW = visuVariables[exprFillColor]; // convert to RGB exprFillColorRGB = TODOCONVERT(exprFillColorRAW); // overwrite fill_color fill_color = exprFillColorRGB; }
I feel like this case is not supported yet, so we could read the variables from xml and look for the correct one at this place, would this work?
I will add some info that we already gathered: The parsing most likely needs to be added in codesys.pp.js at line 741. var exprFillColor = []; var expr_fillColor = $myMedia.find('expr-fill-color'); if (expr_fillColor.length) { exprFillColor = parseExpression(expr_fillColor); // Read out value from visuVariables? // convert to RGB? // overwrite fill_color }
How can we add support for expr-fill-color?
TOD# not displaying correct?
Tagging r131
Release r131
next test
next test
improve build process and documentation
Supported Elements and Features
bugfix: generation of WebVisu.html via release.sh failed because of a comment gpp could not process
some cleanup
bugfix: first row and column of table now fixed;
add tables (full support, scrollbars are now displayed if array is bigger than the element)
add tables (basic support)
bugfix: fixed some issues that caused incompatibility with IE11
subvisu fixed,scrollable: scrollbars are only drawn if needed;
Supported Elements and Features
subvisu code refactoring
bugfix: scrollbar element caused crash
subvisu-element fully supported, not refactored yet
scrollable subvisus now supported (but scrollbar arrow-buttons are not displayed yet)
subvisu scaling now supported, bugfix: frame now in front of subvisu elements
bugfix: signed integer variables were sometimes interpreted as unsigned
subvisu complete rework (first idea had some flaws),
basic subvisu support, for now everything is interpreted as "fixed with scrollbar", still some minor bugs
created branch for subvisu development
Supported Elements and Features
Supported Elements and Features
Supported Elements and Features
WebVisuPlus
Home
Supported Elements and Features
Supported Elements-Features
Scrollbar element is not supported
#30 add scrollbar element
add dashed lines for simpleShapes, polygons, polylines, bezier
add piecharts
add placeholder for currently not implemented elements
add polygon text
add bezier curves
Hi all, Frank, great tool! A couple of notes of feedback to hopefully help the group. I am only using this for basic diagnostics (on/off/values/and colors) and it works fine, I can't speak for more advanced items. Here are the details. Tested on... 1. Wago 750-829 2. Windows 10 3. Chrome 4. FireFox NOTE: The base web visu screen must be called 'plc_visu', otherwise the 'Error, disconnected from PLC' message will appear.
Tagging r102
Add new tests to the test-project
Release r102
Update documentation files
Correct svnversion marker
Rework for compatibility to Sabo
WebVisu seems to be frozen after timeout on slow connections
With r97 I've added an Error-Overlay to display a Messagebox in such cases. In addition there is an automatically reconnect attempt every 10 seconds.
Tagging r97
Release r97
Testprojekt erweitert für embedded Visu
#39: Add ERROR-Overlay and automatic reconnect on lost connection
Add english CoDeSys Visu Doc from 3S
WebVisu seems to be frozen after timeout on slow connections
Correct Markdown formatting
Add english version of DEV_GUIDE - thanks to Aliazzz
IMHO this issue is a showstopper... Could you please throttle the priority of this issue to most urgent?
Add Log for unknown Expression-Operations
Correct Expression-Evaluation; improve german DEV_GUIDE
Update Testprogramm und Abzug Targetfiles
Release r87
Hidden buttons remains active
With r87 this issue should be finally fixed.
With r87 this issue should be finally fixed.
Mit r87 wurde der letzte Teil des Klick-Handler-Rework eingecheckt.
Click-Handler needs rework
#38: Finished reworking Click-Handling
Überarbeitung des kompletten Klick-Handlings; bisher nicht vollständig getestet
Test erweitert
Click-Handler needs rework
See #38 for further informations.
See #38 for further informations.
The Changeset only fixes a part of the problem and shows up others. See #38 for further informations.
Click-Handler needs rework
Release r83
#37: Fix a problem with string representation and backslashes
Release r81
#37: Fix a problem in the release process
#35: single action <INTERN ASSIGN> implemented
Action "Execute program" not handled at all
Action "Execute program" not handled at all
New Revision r78
Dynamic Text not working when XML-File is outside Projectfolder
With r78 only the filename part of the path is used and the ".xml" is replaced by "xml.zip" when the visu is packed.
#37: Dynmic Text file outside working folder and possibly packed
Dynamic Text not working when XML-File is outside Projectfolder
Dynamic Text not working when XML-File is outside Projectfolder
Dynamic Text not working when XML-File is outside Projectfolder