I am using Storybook version 3.3.15 on Windows 7 running node version 6.3.1 and npm version 3.10.6.
On running storybook, I see 'No panels Available' message in the bottom of the page where actions panels are rendered. I have imported addon-actions in addons.js: import #storybook/addon-actions/register and the module is also present in node_modules folder. I am not getting any errors regarding this during webpack compliation or in browser console.
How do I make the Action Panel appear?
Note: I cannot update the Node and NPM versions because I am working on a professional level app wherein lots of people are involved and its a very big codebase.
In my case they were simply hidden and in the wrong orientation. Had to use the D and A keyboard shortcuts to make them appear again.
in my case just hitting d worked
For me the whole main menu disappeared at one point. The only thing that helped was running sessionStorage.clear() in the console and then refreshing the page.
First of all, check if you have the addon panel set to show/hide in the dropdown menu at the top left of the Stoybook UI screen, also check the dropdown item called 'change addons orientation' (mine was changed and was bumped off screen because of screen width).
If that doesn't work, try setting the options in the storybook config.js file:
In the Storybook config.js file you can add an options parameter for some default settings, this includes setting the visibility and position of the addons panel.
import { addParameters } from '#storybook/react';
// settings for storybook - show and position addon panel
addParameters({
options: {
// display panel that shows addon configurations
showPanel: true,
// where to show the addon panel --- #type {('bottom'|'right')}
panelPosition: 'bottom',
}
});
In my case I was missing the .storybook/addons.js file. It looks like this became a requirement in a recent version because the actions add-on used to work fine for me initially.
To clarify potential confusion:
As the documentation specifies, you need to have a addons.js file in your hidden .storybook/ directory (most likely at the root of your project) even if all it contains is just this 1 line.
import '#storybook/addon-actions/register';
I Just found out it by trying different keys on my keyboard:
If you press "S" - it switches Sidebar in StoryBook Of
and On! Try it!
My Browser: Chrome, Operating system: Mac OS
In Mac I solved it by pressing fn + s.
I was having this problem; hitting S would shift my components without showing the sidebar, and even after clearing my localStorage and sessionStorage I could barely see the edge of my sidebar.
Then, I realized that I had zoomed in to see my components more closely, and that the sidebar was hiding/showing, but just off-screen.. I just needed to zoom out. 🤦♂️
Sharing here in case anyone makes the same mistake.
I had a similar problem and installing #storybook/addons (in addition to the steps you mentioned) fixed it.
Run:
npm i -D #storybook/addons
I use PyInstaller to get a single file executable from my python script.
as seen in this thread : Pyinstaller setting icon
it is not that complicated to add a icon to the .exe file.
Except that it adds 2 icons :
* when I show "Medium icons" (or bigger) in the windows explorer, then I see the standard PyInstaller icon
* when I show "small icons" (or smaller, like in "details view") then I get the icon I specified.
With a "iconviewer" I can see that the default icon is mine, but the PyInstaller icon has ID=1
is there a method to get avoid this second (ID=1) icon ?
My icon is already 256x256 big...
According to this answer https://stackoverflow.com/a/3244679/4316500 Windows 7 does not need bigger icons.
It seems that the problem solve itself alone...
The day (and a reboot) after my long time search on that problem, the icon was OK.
Perhaps the Windows cache for icons where preventing me to see the right icon.
Still not clear because I'm also sure that my iconviewer saw 2 different icons. Now, I have twice the same (and wanted) icon. It's twice too much, but nobody sees it.
I just switched over to Sublime 3, using it as a my current text editor. I downloaded the theme "Coffee Dark Roast" (which I think looks pretty slick) from GitHub and the theme appears to be working just fine except for the fact that it is not being applied to the Side Bar that shows open files. Also, the theme is not being applied to the Console at the bottom of the screen either.
Does anyone have a solution, or reason as to why the theme is not working for the Side Bar and Console?
MacBook Pro OS X 10.9.5
Check your user preferences and make sure that you don't have another sidebar theme present. This is usually the case.
I set the window title by
QWidget::setWindowTitle("test");
so the title of the window is "test". But in the taskbar it's displayed as "unknown". What's the correct way to set the taskbar name?
Edit:
I use Gnome3.4.2 and just found https://bugreports.qt-project.org/browse/QTBUG-22274. But for me there also the binary name isn't displayed; only "unknown".
EDIT2:
I tried it under Xfce and it worked.
I think you're not installed libgtk dev packages when compiling Qt. Make sure you have libgtk dev packages are installed and try compiling Qt5 again.
I am using QtWeb browser (www.qtweb.net) for my development. When I try to open the following URL in the browser, the drop-down menus of the buttons do not open up:
http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/form/test_Button.html
This issue is not seen across other browsers.
Any workarounds/suggestions/ideas would be appreciated.
I encountered the same problem. Interestingly, the popup menus do not work since version 1.7.1.
This is not bug of dojo. This is some mistake in QtWebKit. The problem in touchpad device that defined by default in precomiled qt webkit libs (even if the touchpad does not exists physically).
Temporary solution is to edit dojo/has.js file (find this lines in dojo >= 1.7.1):
if(has("host-browser")){
var agent = navigator.userAgent;
has.add("dom-addeventlistener", !!document.addEventListener);
has.add("touch", "ontouchstart" in document); <<<<< Comment this line
has.add("device-width", screen.availWidth || innerWidth);
has.add("agent-ios", !!agent.match(/iPhone|iP[ao]d/));
has.add("agent-android", agent.indexOf("android") > 1);
}
Here another solution (more painfully):
Link to the helpful message source
You must recompile QtWebKit with DEFINES+=ENABLE_TOUCH_EVENTS=0 that defined in WebCore/features.pri.
Then you qt web projects will be work properly!