Those.
You are calling things that affect the UI after setViisble() is called -- a
Swing no-no. Put things that affect the UI into an invokeLater call; look
it up.
While you're at it, I think you're still supposed to get the content pane
from the frame for adding components... And I don't think creating things
in the constructor is a good idea.
import java.awt.BorderLayout;
import javax.swing.JFrame;
import javax.swing.JLabel;
import javax.swing.SwingUtilities;
public class SwingTest extends JFrame
{
public void createUI()
{
setDefaultCloseOperation(DISPOSE_ON_CLOSE);
SwingUtilities.invokeLater(
new Runnable()
{
public void run()
{
getContentPane().setLayout(new BorderLayo
I'm not sure I understand your question ..
to implement drag you can use UIGestureRecognizer
This is a simple tutorial
Magento upgrades are just file overwriting, so any Zend component which you
would like to upgrade or add can be done under lib/Zend/ if it will not be
replaced by a subsequent upgrade (note that Magento releases are pegged to
specific versions of ZF1).
That said, it's possible to provide the specific Zend component version you
need under app/code/local/Zend/ because of include_path bootstrapping, and
this will work fine.
Strange but possible you could use a WebMarkupContainer or perhaps a Border
WebMarkupContainer it respect his inner content regardless if its valid or
not
Border useful for decorate markups.
however your example is an invalid HTML, only God knows how that thing
going to be rendered by the browsers
You can use SWFLoader. Either place one inside your UIComponent, or if the
MovieClip is the only thing inside the UIComponent, you can use the
SWFLoader instead of the UIComponent.
Use the load method to load a SWF or an image, eg:
mySWFLoader.load("path/to/the/movie.swf");
If you don't want to load at runtime, you can embed the SWF in the Flex app
instead. And in this case you only need an Image component with the source
property set. eg:
<mx:Image
You need to take the time to read the vlcj wiki
You can not simply add a lightweight transparent JComponent on top of
the heavyweight video surface Canvas component - it will not work.
Which is what I suspected from the earlier post on the same subject
@MasterAM is correct about the private.
On a somewhat related note, router.php does not like variables sitting
outside of functions. I tried to add a global array but it was not
accessible. Instead I made a function to return the array.
In C++ Builder XE6, released a few days ago (mid-April 2014), you can now
create 64-bit packages in C++.
Old outdated answer (valid for C++ Builder XE3, 4 and 5):
64-bit compilation is a missing feature for C++ packages in XE3 and XE4.
For Delphi, you can target Win32, Win64, OSX and (I think) iOS for
packages.
For C++, you can only target Win32 and OSX, even if you have the 64-bit
compiler installed. This is documented for XE3, and is apparently not
fixed in XE4 either.
There was no QC report for this, so I have added one. Please feel free to
vote for it. My rationale for its importance is that packages are an
important part of the Delphi / VCL ecosystem, especially for components.
While you can use Delphi-created 64-bit packages in your 64-bit C++
project, this means you can't
I think the problem you have is that you are creating the
wix:ComponentGroup elemnts within the xsl:for-each
<xsl:for-each
<wix:Fragment>
<wix:ComponentGroup
You really only want one wix:ComponentGroup for each wix:DirectoryRef which
means you probably want two nested xsl:for-each statements, one for
wix:DirectoryRef and one nested inside for wix:Directory
Try something like this
<xsl:template
<xsl:copy>
<xsl:apply-templates
<xsl:for-each
<wix:Fragment>
<wix:ComponentGroup
<xsl:for-each
It's already built in and will work with your custom field constructors.
It's actually documented under the Rendering an <input> element on
the page you linked to.
Note: All extra parameters will be added to the generated HTML, except
for ones whose name starts with the _ character. Arguments starting with an
underscore are reserved for field constructor argument (which we will see
later).
So doing something like this:
@inputText(
myForm("user"),
'_label -> "User",
'size -> 30,
'placeholder -> "User Name"
)
Will output HTML like this:
<input id="user" name="user" size="30" placeholder="User Name">
It's documented somewhere, but if you want to do data attributes then you
have to do this:
@inputText(
...
Symbol("data-some-attribute") -> "val
Try This,
On Joomla 1.6 onwards the component details storing table is #__extensions
Also you have set the details #__menu table too.
Hope this may help you..
I didn't understand the comments. Now I understand it.
The "obslik" here isn't equal to the observematrix1. Before using
Viterbi_path function, we should compute the obslik:
obslik = multinomial_prob(data(m,:), observematrix1);
the data matrix is the observematrix0, observe-matrix before training.
Am I right?
This is because your not able to have your C++ code call into C#.
You can only have C# call (and return) into C++.
With CSS, overriding the top container position rule for the
dock-container-top class:
.ui-dock-container-top {
position: absolute !important;
}
Hope it helps!
You can iterate over the components via FindComponent. In the example below
Self as the Form is given as Owner.
Procedure SetChecks(AOwner:TComponent);
var
x:Integer;
begin
for x:=1 to 5 do
TCheckBox(AOwner.FindComponent('check' + IntToStr(x))).Visible :=
TDateEdit(AOwner.FindComponent('date' + IntToStr(x))).Date
<>StrToDateTime('00:00:00');
end;
procedure TForm1.Button1Click(Sender: TObject);
begin
SetChecks(Self);
end;
The <ui:include> doesn't extend from UIComponent. It's a tag handler.
It does thus not support the rendered attribute at all. It's also nowhere
listed in the tag documentation.
<ui:fragment> is indeed an UIComponent. So basically you end up with
all those 3 include files being included during view build time and thus
all 3 physically end up in JSF component tree. It's only the HTML output
which is conditionally rendered via <ui:fragment rendered>. You still
end up with duplicate component IDs from those includes because they all
end up in JSF component tree.
You should be using a taghandler like <c:if> instead of
<ui:fragment> to conditionally build the JSF component tree.
So, theoretically, this should do for each of them:
<c:if test="#{filtersPopup.fi
It is very rare that one individual layout manager will meet all your
needs. Instead you could use a compound layout approach.
That is, separate each individual layout requirement into a separate
component, with it's own layout manager. Then added all these to your
master component, managing the overall requirements.
As an example
import java.awt.BorderLayout;
import java.awt.Color;
import java.awt.Dimension;
import java.awt.EventQueue;
import java.awt.GridBagConstraints;
import java.awt.GridBagLayout;
import javax.swing.JFrame;
import javax.swing.JLabel;
import javax.swing.JPanel;
import javax.swing.UIManager;
import javax.swing.UnsupportedLookAndFeelException;
import javax.swing.border.LineBorder;
public class SimpleGridBagLayout {
public static void main(String[] args) {
To extract part of a string, use a regular expression: in R, type
help(regex) and help(grep) for instructions.
>
test=data.frame(ID=1:3,Code=c("101ABC","021DPA","FCA123"),Mixture=c("BD","AA","IO"))
> test$v1=gsub("[A-Z]*","",test$Code) # this returns the Code column
with capital letters removed
> test$v2=gsub("[0-9]*","",test$Code)
> test$v3=paste(test$Mixture,test$v2,sep="")
> print(test)
ID Code Mixture v1 v2 v3
1 1 101ABC BD 101 ABC BDABC
2 2 021DPA AA 021 DPA AADPA
3 3 FCA123 IO 123 FCA IOFCA
(There's probably a neater solution using the stringr package, but I
haven't used stringr myself.)
Use a ASP fileUpload, and display the uploaded file in an ASP image
control.
HTML (ASPX)
<asp:FileUpload
Code behind
FileUpload1.SaveAs("filename")
Any relative client ID in <f:ajax render> is evaluated relative to
the parent naming container of the component it's been attached to. In this
construct, the <f:ajax> ultimately ends up being attached inside the
composite component, which is by itself a naming container. However,
there's no component with ID out2 inside the composite. That explains your
problem.
To solve it, you'd need to specify the absolute client ID. For example,
when it's actually inside a <h:form:
<f:ajax
If it's however more complicated than that, consider binding the component
to the view and dynamically referring its client ID:
<h:outputText id="out2" binding="#{out2}" ... />
...
<f:ajax execute="@all" render=":#{out2.clientI
While Ext.ComponentQuery queries for all underlying Components (you may
define a traversing start as second param after the query string) it also
allow you to query by a various set of params, attributes, pseudo classes,
functions, etc. Full Reference and always result in a set (array)
compinstance.GetComponent('itemId') only queries the direct childs of the
calling component for the itemId property and will always return one
reference or null. Note that the itemId need only to be unique to all it's
siblings.
So yes GetComponent() will be a bit faster.
I don't think that there are huge pros and cons. GetComponent() cannot be
used that often because you may not only looking in level. Take a menu
which groups the the buttons, GetComponent() will only find the group but
not the anything wit
UIComponent#getAttributes() is a very special map. On a given key, say
"foo", it first evaluates #{component.foo} as a ValueExpression which
implicitly invokes UIComponent#getFoo() method. See also the javadoc. That
totally explains the infinite loop. If the getFoo() method was absent, then
it'd just have continued to look in the "static" map (which you can control
by overriding UIComponent#getValueExpression()).
You need to solve your concrete functional requirement differently. I have
actually had a hard time in wrapping my head around your concrete
functional requirement, but I believe that you actually need to define
separate properties with separate getters/setters, all properly delegating
to the state helper:
public String getLocalName() {
return getStateHelper().eval("localNam
In the Bayes Net Toolbox, what is called Dynamic Bayesian Network is in
fact just a Temporal Bayesian Network in which we can specify a different
structure for the first time-slice: :.
[...]
To specify a DBN, we need to define the intra-slice topology (within
a slice),
You can perform the equivalent of the spline fit performed with cftool with
fit, see for instance here, here, or here:
% perform spline fit without cftool
ft = fittype('cubicspline');
coeff=fit(x,y,ft);
% use plot to display the interpolating polynomial
% (relying on internal plot settings)
figure
h=plot(coeff,x,y,'o');
% extract the *interpolated* curve from the figure
xi=get(h,'XData');
yi=get(h,'YData');
Replot it just to show that we can:
But if you just want to interpolate do as Fraukje explained here. Define a
finer grid on x and use the interp1 function, as in the following example
(same x,y input data as before):
% interpolate
Ni = 100;
xi = linspace(x(1),x(end),Ni);
yi = interp1(x,y,xi,'spline');
Now xi,yi is the interpolated data:
I have found this technet blog that describes the steps that need to be
taken to deploy a code activity in a Visual Studio 2012, SharePoint 2013
Workflow:).
There is no weird symbol, only square brackets. Your pdf viewer must be
using some weird fonts. The code of the actual examples are:
## online 35
mInput(:,[4 8 12]) = []; # delete column 4, 8 and 12
## on lines 54 and 55
mInput(:,1:nValiSets) = [];
mOutput(:,1:nValiSets) = [];
That's just an open square brackets [ followed by a closing square brackets
] which translates to " replace the values of this indexes with nothing".
You can find some basic examples on usage of NETLAB online here, the
following is just the header:
A Simple Program The "Hello world" equivalent in Netlab is a programme
that generates some data, trains an MLP, and plots its predictions.
The online demo is a brief version of a longer demo available with the
program, and uses functions mlp and mlpfwd.
In the downloads page you'll find that you can download help files, too.
If you get stuck you may (perhaps as a last resort) want to contact the
authors.
edit
I understand that pointing to help files might not be what you were looking
for. As you rightly point out, there is little documentation (perhaps more
importantly no demos that I could find) on performing backpropagation, and
definitely not with 3 layers. The available func
Basically they use reverse dns lookups against 100+ dns server which do the
black listing.
Another nice site to check if your server is blacklisted it.
use nuget to add the modernui to your project.
all forms inherit from MetroFramework.Forms.MetroForm
setup your toolbox panels with the "choose", you have to use browse to
navigate and
find the metroframework .net dll in the packages folder. pick the
one for your build, so .net4 for .net 4 ..etc
that gets you a toolbox panel with "Metrobutton" ..etc.
from that panel drag drop a MetroStyleManager control onto your form. It
will keep all the
styling on your page the same. then you can set the style and theme
once in the constructor. I suggest you make those objects public,
then its easy to pass style and theme to any sub windows with ease.
there is a limited set of controls, but should get you started. (I've just
played with it for a few hours)
I had the same issue and almost were desperated. But then I stumbled upon
this post. At the end it seems even worse then mentioned because it is not
enough to put your resulting assembly into a different location without the
"#". You have to store and compile your whole solution in a path without
the "#".
My problem was that all my C# Projects were located in a path with
"somedirectoryC#Projectname.....". Compiling and referencing the resulting
assembly was working fine but when I tried to add components from the
assembly to my Toolbox the upper mentioned error message arose. After
reading this post here I first tried to copy my resulting DLL into a
different path after compiling but that didn't change anything. After
giving another try I changed the whole project path to get rid of the
There is nothing magic in WinForms drag & drop. You can reference the
same classes from System.Windows.Forms. If you are going to roll your own,
I would suggest looking at the Model View Presenter pattern.
Here is a nice article comparing Java Swing and WinForms:
To question a, you can use callback or observer instead of event
callback
Assume we have Component A and B, and the instances are a and b. Use
callback will make it no context needed.
b.callback = a.handler;
b.doSth();
// component define
Class A {
public function handler(param:*):void {//you can have your param here
}
}
class B {
private var _callback:Function;//here you can use a array to save multi
callbacks.
public function set callback(value:Function):void {
_callback = value;
}
public function doSth():void {
//do something
if (_callback != null） {
_callback.apply(null, [some data]);
}
}
}
Observer
Here is some introduce to Observer, it looks like callback in some way.
Observer
Functionally, it doesn't make any difference. Technically,
UIComponent#getAttributes() allows the developer to not worry about the
exact component type while getting/setting the attributes.
Look at your particular example with disabled="true". The UIComponent
superclass doesn't have any isDisabled() method at all. You'd need to
perform an instanceof check on e.g. HtmlInputText before you can cast it
and finally invoke isDisabled() on it. The getAttributes() is then much
easier in order to be independent from that. A lot of UIComponent related
methods in standard JSF API take or return UIComponent superclass instead
of a specific type.
In properly designed components, both delegate under the covers ultimately
to the same, the UIComponent#getStateHelper().
The UIComponent class has a isCompositeComponent() helper method for
exactly this purpose.
So, this should just do:
for (UIComponent child : component.getChildren()) {
if (UIComponent.isCompositeComponent(child)) {
// It's a composite child!
}
}
For the interested in "under the covers" workings, here's the
implementation source code from Mojarra 2.1.25:
public static boolean isCompositeComponent(UIComponent component) {
if (component == null) {
throw new NullPointerException();
}
boolean result = false;
if (null != component.isCompositeComponent) {
result = component.isCompositeComponent.booleanValue();
} else {
result = component.isCompositeComponent =
(component.getAttributes().containsKey(
Most likely you have added Ninject.Extensions.Interception but not any of
the concrete implementations Ninject.Extensions.Interception,DynamicProxy
or Ninject.Extensions.Interception,LinFu
The command fuzzy launches the Fuzzy Inference Systems editor, a GUI
supplied with Fuzzy Logic Toolbox. Compilation of Toolbox GUIs with MATLAB
Compiler is typically not supported, and as detailed in the documentation
for MATLAB Compiler, this is true of the GUIs within Fuzzy Logic Toolbox.
I must say, I think the message you're getting in the mccExcludedFiles.log
file is mostly misleading - all of those things could cause a file to have
been excluded, but in this case the only relevant bit is at the end,
"(because of toolbox compilability rules)".
After checking I found that only I need to put the following before the
class declaration:
<System.ComponentModel.DesignTimeVisible(False)> _
Public Class ControlClassName
End Class
imgSize is a variable defined in the model workspace. To avoid using it,
you can simply look under the mask of the Effects subsystem. It's a block
composed of smaller blocks. You can navigate under its mask and extract
what you need.
Back to the original question: to blur, just use fspecial with the 2-D FIR
block from the Filtering library. You can use a 2-D gaussian mask returned
by the fspecial command or you can grab a 1-D filter and use the separable
option on the 2-D FIR block in order to accelerate the computation since
the 2-D gaussian is separable.