Why a button in LWC component vanishes when its running in the debug mode but the same is shown in the normal mode
<lightning-button-stateful
variant={showButtonVariant}
selected={isButtonDisabled}
label-when-off="Add"
label-when-on="Added"
disabled={isButtonDisabled}
title="Add account"
onclick={handleAddClick}
class="slds-m-left_x-small"
></lightning-button-stateful>
Button is working fine in the mode where debug is not enabled. But when debug mode is enabled for the user, then it is not shown.
Related
I have watched a few tutorials on adding OnClick events to buttons in UI panels and they all have a panel in the button section where you can add a scrip to the on click event.
However, in my panel all I have is an expandable list that shows Persistent calls with no option to add any script (image for reference)
My Panel, with no option to add a script to OnClick Events
Your Inspector is in Debug mode which exposes all fields without applying any property drawers and editor scripts!
See Unity Manual - Inspector → Toggle Debug Mode (bottom section)
Toggling Debug Mode
Normally, the Inspector window is configured as an editor for the selection’s properties. But sometimes it’s useful to only see the properties and their values. When you activate Debug mode, the Inspector shows only the properties and their values. If the selection has script components, Debug mode also displays private variables, although you can’t edit their values
You can toggle Debug mode for each Inspector window individually.
To turn on Debug mode, click the More Items ⋮ button to open the context menu, and select Debug.
To return to Normal mode, click the More Items ⋮ button to open the context menu, and select Normal.
In theory you could still add elements to the Persistent Calls list by editing the size value ... but really just switch back to normal mode ;)
I am trying to print some text in console of unity but no text gets printed in the console. there is an option of attach to unity and play but even after clicking on it nothing gets displayed.
Are you not able to see the console printouts in Unity? Debug.Log("message") and/or print("message") should work. You need to enable your console to view them. Enable it by going to Window -> General -> Console in Unity, and enabling debug messages by selecting the message tab on the top left of the console window.
Here is how to enable your console.
Here is the tab you must select so debug logs or normal print messages are shown in the console log. The tab to the right of the messages are warnings and to the right of that are error messages.
Attaching Visual Studios to Unity when in play mode is only needed when you need to debug your code. It is especially useful when using breakpoints and walking through code to determine complex issues. If you have a debug print message in code, make sure the script is on a GameObject that is enabled and active in your scene. Once that is done, just hit the Play button in Unity.
I have looked for a solution but couldn't find one, recently I switched the Explorer in VSCode from the LHS to the RHS and it works better, the problem I am now having is that when I open the terminal I get a debug console on the left - see picture below.
Is there a way in which I can disable/hide the Debug Console part of the terminal? It is always maximized when I start a new console and I can't set it to minimize.
Either choose Reset Location in the context menu or just drag the Debug Console header back into the upper part of the Panel (like to the right or left of the Terminal header).
At some point you must have dragged the Debug Console header into the body of the Terminal (when Terminal was active and into the left half of its view).
You'll also notice that the option to Hide 'Debug Console' is disabled in your first situation - that is a hint of sorts - it is actually within the Terminal view and so cannot be separately hidden from its context menu.
Click on the debug tab and drag it to the top.
In Ubuntu 16.04 with workspaces enabled I'm having trouble getting applications switcher/workspaces to behave in a friendly manner if some windows are in full screen mode.
Say I have two workspaces A and B.
A has two windows open: browser and terminal 1 in full screen mode.
B has one window open: another terminal 2 in full screen mode.
I leave workspace A with browser window being active and move to workspace B to work in a terminal 2.
Then I move back to A but end up in a state where (1) no particular window is active, (2) terminal 1 is at the foreground, NOT the browser.
Then I need to either Alt-Tab to make terminal 1 active or click in it, and Alt-Tab to get back to the browser.
This does not seem to be the property of the application switcher --- I've tried the default plugin one, "applications switcher" and "static application switcher" with no luck.
The problem does not occur if applications are not in full screen mode --- if they are in maximized state everything is fine.
I grabbed the Ionic side menu starter template from Github. I created a fresh project in IntelXDK and copied the side menu code in. The app is working. The side menus look and works fine. It runs fine except for the Login menu. The modal shows, you can see the two form fields, but then nothing happens from there. You cannot click in either input field. You cannot click the submit button. You cannot click any menu button either. It appears to freeze.
This is just the default template code. Nothing else. I'm running in the IntelXDK emulator and/or my connected Android phone, same behavior on both.
What's happening? :-/