Please look at this plunker: http://embed.plnkr.co/hvQ6gflnNrpdcZfXSLMH/
When selecting an option for the first time, the option is selected, but the select2 shows empty label. Only when selecting the option for the second time the label appears.
I've checked the select2 without the use of angular-ui-select2 directive, and it works perfectly. I tried several versions of select2, and also tried ui-select2 versions 0.0.4 and 0.0.5.
Opened an issue on github: https://github.com/angular-ui/ui-select2/issues/239 but no comment so far, so I thought maybe the community could assist.
Thanks,
Lior
Right now, ui-select2 is incompatible with
https://github.com/angular-ui/ui-select2#working-with-dynamic-options
If you need an alternative that does work with dynamic options, you can check out https://github.com/angular-ui/ui-select. It's a native AngularJS version of select2 & selectize.
Related
I installed the last version of OpenContent Module, and I add some items using catalog template, but when I try to filter the content using Filter Settings, it doesn't work. Seems that for some reason the module doesn't find the results.
Someone knows how it works or what I doing wrong?
Filter Settings
for some reason only accepts lowercase values and no symbols like: &, #,... try to change the "Membership" for "membership".
I am trying to develop a dashboard for my client where I have to use several google web components. My first approach is to show up a simple analytic query for which I am using this:
<google-analytics-query
ids="ga:xxxxxxxx"
metrics="ga:sessions"
dimensions="ga:country"
sort="-ga:sessions"
start-date="2015-10-01"
end-date="2015-10-31"
max-results="5">
</google-analytics-query>
But nothing is visible!
I am referring to https://elements.polymer-project.org/elements/google-analytics?active=google-analytics-query
What's going wrong?
UPDATE
I also tried the following code to render google-analytics-chart output ended up with a big white box.
<google-analytics-chart
type="area"
ids="ga:88814676"
metrics="ga:sessions"
dimensions="ga:date"
start-date="2015-10-01"
end-date="2015-10-31"
max-results="5">
</google-analytics-chart>
This question as also asked on the Github repo for the <google-analytics> element. You can see the answer there:
https://github.com/GoogleWebComponents/google-analytics/issues/29#issuecomment-157367824
The gist of the problem: using the <google-analytics-chart> element require authentication via the <google-signin> element in order to work.
Im using zk version 7.0.2 and I need to disable all styles/themes from zk, then I need to put my own style css. There is a way to do this?
I tried to put some css files but it doesnt change. In some docs I've found shows me about creating my own theme using LESS but it doesnt work.
Thanks
Yon can specify the disable-theme-uri element in zk.xml, for more details, please take a look at this document.
I'm trying to use Aptana Studio 3 instead of phpEd. But I'd like to have the code coloring like in Dreamweaver. I made these changes in phpEd, but I can't find where to change it in Aptana.
Also, I installed the jquery bundle, but I can't to get it working...
Thanks for your help.
Preferences:Aptana:Themes. Figuring out what keyword corresponds to what display object can be a bit tricky, but it is all there.
There's actually a ticket already filed to add a theme that matches Dreamweaver: https://aptana.lighthouseapp.com/projects/35272/tickets/1508-create-dreamweaver-color-theme
I'm looking at it now, but I'm running into some internal bugs (namely https://aptana.lighthouseapp.com/projects/35272-studio/tickets/2357-scope-selectors-with-portion-prefix-match-arent-matching-properly) that I need to fix before I can finish. In any case it should be in Studio 3.0.2 and hopefully I'll fix it today and it'll be in tomorrow's nightly (here's how to get nightly builds: http://wiki.appcelerator.org/display/tis/Changing+the+Update+Type).
As for editing themes yourself, you can see the current scope at the cursor by doing Commands > Bundle Development > Show Scope. Then use scope selectors that match that sort of scope (we adopt Textmate's scoping/theming rules: http://manual.macromates.com/en/scope_selectors)
Could you finally get your theme?
If you want to create your own theme then first go to: Window->Preferences->Aptana Studio->Themes
To create a new theme just click on the "+" sign next to the themes
list.
To add elements to your new theme right click the text in your
editor and click Commands->Bundle Development->Show scope.
Copy the last section you see to the right of the hint window that
appears.
In the themes elements list click the "+" located at the bottom of
the dialog box (next to "Scope selector")
Give a friendly name to your new element.
Assign foreground/background colors to your new element.
Paste the element's scope in the "Scope selector" input box (make
sure your new element is selected, if not, click on it).
I created a theme for PHP, CSS, HTML, JS and XML editors, similar to the old aptana 2 colors. If you want to get it you can write me to jgarcias.cr at gmail dot com.
Cheers.
I've recently started working with an application written using Adobe Flex 3. We're using several deprecated functions and unfortunately we can't remove these dependencies.
The documentation says to set -show-deprecated-warnings=false into the Compiler Additional Options. This isn't accepted, but I've found that using -show-deprecation-warnings=false will be accepted by the dialog, but gives an error about declaring the option twice when I try to compile the project.
Ideally, I'd like a way to disable the warning on a case-by-case basis. Failing that, can anyone help me to disable the warnings either per-file, per-project or globally?
As an update for recent versions, I added a compiler option in FlashDevelop:
-show-deprecation-warnings=false
This worked for me.
This link suggests that it doesn't work properly anyway, and the only real answer is to turn off warnings altogether.
Adobe Jira 13569
You can turn off warnings by using a custom flex-config.xml file for each project / globally. Just point the compiler at the right file.
I've found a partial workaround: filter the warnings from the 'Problems' tab. This doesn't get rid of the next-to-the-source warning markers, but it's the Problems tab which I'd like to be clean.
Click the filters button on the Problems tab, change 'Description' to 'doesn't contain' with text 'deprecated' and hit OK.