About MrAdam1983

MrAdam1983 · ‎08-24-2023

@webiq-sk wrote: "The issue is that internal to the js code, there is no way to access the .value of an item and read that as an integer." Sure there is - there are two ways available: 1. When you only need a one-shot read: readDirect 2. When you want to react to continuous item changes: subscribeItem Here is the corresponding code from the scripting demo ("demo-item-subscribe") that illustrates this: // Define our item names to use - it's best to put them here and not somewhere in the code below // for easier changeability and understanding const observedItemName = 'ls-observed-item'; // See below let subscriptionToken = null; // Get a reference to the ItemManager const im = shmi.requires("visuals.session.ItemManager"); // Create a new instance of an item handler to use and define a function that will be called // asynchronously by the framework whenever the item value changes (or is received initially) const myItemHandler = im.getItemHandler(); myItemHandler.setValue = function (value) { console.log("[LS demo-item-subscribe] The value of the item has been set to " + value); }; // Obtain a subscription token. You ALWAYS have to store this token and call the appropriate unlisten function // when you no longer need it, in this case when the LocalScript will be disabled (see below) // If you do not do that this will likely cause memory leaks (https://blog.logrocket.com/escape-memory-leaks-javascript/) // leading to more and more RAM used in your HMI until the amount of free RAM will be exhausted and the browser will crash // The WebIQ Visuals framework always calls the onDisable function automatically when your LocalScript should not be running anymore, // e.g. when it has been included in a screen view and the user switches to another screen. subscriptionToken = im.subscribeItem(observedItemName, myItemHandler); /* called when this local-script is disabled */ self.onDisable = function () { if (subscriptionToken) { subscriptionToken.unlisten(); // Remove the listener and tell WebIQ Server to stop sending us item updates } self.run = false; /* from original .onDisable function of LocalScript control */ }; And if your item does not have the type integer in your PLC you can of course cast it with JavaScripts parseInt() method into an integer value. I am sorry for the things I said while i was pretending to be a programmer. this was certainly the fix for everything i was fighting. i had tried to implement this yesterday but must have really messed it up. my second attempt today went much better. it works, does exactly what I need it to do. I am now in the refinement process and will start add additional features. i appropriate the guidance.

MrAdam1983 · ‎08-22-2023

short answer - no. From a post I made with the same question, among others. "2. Line breaks in Labels Line breaks in labels are not supported currently. As a workaround you can however empty the label field, disable the "Auto" button and put a simple IQ Text widget where you want to have the "label" as that widget supports line breaks. Usually CSS would be an option, but in labels the line breaks are removed automatically by the widget's JavaScript code so overriding with CSS is not possible here, unfortunately." WebIQ Development - Am I just over thinking this, ... (boschrexroth.com) the solution harckens back to how we do it in FactoryTalk for similar issues; back a trasparent button on top of a lable object, becuase for some stupid reason a lable object can line break while a button cannot. I believe neither can truely center justify either. This exact reason has lead me down the rabbit hole that is custom widgets, which I am sure is a walk in the park if you have been doing object oriented Javascritp for the last 15 years.

webiq-sk · ‎08-22-2023

As I stated before you should never use any "id" attributes in widgets as these make your HTML invalid (even though no browser cares) if the widget is inserted more than once on the same HTML page (i.e. HMI). Please see the link I posted before. You don't need to specify any id for any WebIQ widgets - it's also not documented that you should do that on purpose as it wouldn't make sense as any widget can be inserted multiple times into any HMI hence leading to invalid HTML if you'd use an "id" attribute in your widget HTML code. Specifying the class(es) is not required either, but you probably want to set it to be able to style your widget using CSS. For using shmi.getUiElement(elementName) you always have to specify the data-ui-attribute name you specified (hence it's called getUiElement). This is also specified in the documentation: https://www.smart-hmi.com/user/download/deliver/docs/documentation-webiq-visuals-reference-2.14-3d30/shmi.html#.getUiElement__anchor If you simply follow our tutorial for creating a custom widget exactly you should get to know all of these details - you should not use that manual when reading it for the first time to directly implement your own custom widget, instead you should follow the steps exactly to create the custom widget from the tutorial and only afterwards create your own custom widget: https://www.smart-hmi.com/user/download/deliver/docs/documentation-how-to-simple-control-2.14-3d30/index.html

MrAdam1983 · ‎08-16-2023

right. I have no experince with those standards, this si all new to me and I am on a crash course. with that said, I have objects on the screen now and the latest issue I comperhend but i don't understand how it exist. i will post a new topic for that.

webiq-sk · ‎08-11-2023

The requires changes are documented in the How-To if you want the package to appear in a different directory: Have a great weekend, too!

About MrAdam1983

Re: itemManager Methods and documentation request.

Re: WEB IQ Multi-Line Label for Button Widget

Re: custom widget: why won't this onInit execute?

Re: Cannot get Json for custom widget to Close.

Re: Project path for custom widget creation