Where do I control default Auto behavior of Button.Width and .Height in Visual Basic 2013 designer?

Why does a Button auto-size itself to completely fill a cell in a Grid if I write the code for it in the .xaml-file but fit to the Button.Content if I drag-and-drop the Button into the Grid from the Controls toolbox? Somehow, the software remembers where
the Button came from, but I can't see where, and if I look in the Properties window I can see what dimensions it gets from the auto-sizing, but I can't see any options to change the behavior. Apparently I have to hardcode the dimensions of the Button to fix
it, and that, obviously, is not desirable.
Incidentally, it seems that if I cut-and-paste the code for a Button from one .xaml-file to another, it behaves as if the component was drag-and-dropped into place, i.e. even if the Button fills out the Grid cell in the source project it wil shrink to fit
the Button.Content in the destination project.
Why is this? And where is it that I haven't looked to make the Button behave?
Thanks in advance

Hi，
This is the default behavior in VS. Seems there is no way can control it. May be you can create a custom button to solve your problem.
Best Wishes!

Similar Messages

LabView TEDS library into DLL or ActiveX Control so that I can use it in C or Visual Basic?

We are developing software in LabWindows/CVI and Microsoft C. I heard that LabView can generate DLLs. Can I turn LabView TEDS library into DLL or ActiveX Control so that I can use it in C or Visual Basic development environment?

Technically what you are proposing is possible with LabVIEW. With LabVIEW's application builder, VIs can be built into dlls. Also, LV has ActiveX hooks and so you could create a system for calling into it from CVI. However, this is not what I would recommend.
The LabVIEW VIs have been written to a preliminary version of the IEEE specification (1451.4) that describes the TEDS data which is primarily why I'm advising you against using them. Once the IEEE spec is approved (the current timeline is currently late March), it will become public and you can write your own code according to the specification (or wait for someone else to write it). To help you get started, the spec includes flex and bison code that describes the syntax and structure of the template files
Internally, we've written some C, C++ and Java code to the preliminary version of the spec and we've found that we can duplicate the functionality of the TEDS Library for LV in roughly 2 weeks in any other language.

LR 5.5 double-click behavior on WB sliders (and other sliders in Basic tab)

i recently upgraded to LR 5.5 from 5.4.
sometimes i check the auto-WB recommendation by using the ability to Shift + double-click on a WB slider (in Dev. Module). (this feature was introduced in LR 5, i believe, maybe LR 4.)
before the upgrade, whether the WB sliders were already at a custom setting or still on the "as-shot" setting, you could Shift + double-click on either the Temp or Tint slider and get the "auto" recommendation. Then, you could undo and redo, toggling back and forth between the auto setting and whatever you had before that.
now, however, when i Shift + double-click, before the slider registers the double-click and produces the auto setting, it responds to the first part of the double-click. that means that FIRST it moves the slider a little one way or the other, and THEN goes to the auto setting.
this behavior makes it impossible to toggle back and forth between the auto setting and whatever it was before that. instead, it now toggles between auto and that little adjustment that was registered in the first part of the double-click.
for example:
the Temp slider is set to a custom value of 5200 on a certain photo.
i'm curious what is the auto recommendation, so i Shift + double-click on the slider.
the slider registers the first part of my double-click, moving for an instant to 5384, before understanding that i actually double-clicked and producing the auto setting.
this is annoying in any case, but it's a problem because now when i undo and redo to toggle between my custom setting (5200) and the auto recommendation, it's instead toggling between the auto and 5384. (or whatever value happened to register in the first part of the double-click.)
this changed behavior also affects the other sliders in the Basic tab where you can Shift + double-click to check an auto value. personally, i never use this feature on the other sliders, but i do use it quite a bit on the WB sliders as a step in arriving at my custom WB.
also, i just noticed that it also happens sometimes on black-and-white images, when adjusting the Black and White Mix sliders. (these sliders can also revert to their auto value if you adjust one and then Shift + double-click. this is beneficial for when you don't want to return the whole group of sliders to auto mix.
note:
i do not adjust the sliders by dragging. instead, i mouse over a slider, and use up or down arrow keys to adjust in regular increments (or Shift + arrow key for a larger increment). i find this is a much better way to work for a number of reasons, and especially with large numbers of images. if i want to make a finer adjustment, i just click in the value field of a slider and use arrow keys to go in single-unit increments. (or use Option + arrow key for a smaller-than-default increment.)
For color Temp, camera settings already use 50-degree increments (5600, 5650, 5700, etc.), so they appear in LR with those kinds of rounded numbers, never 5611 or whatever. using the arrow keys to adjust color temp also goes in 50-degree increments, and using Shift+arrow key goes in 200-degree increments. For Tint, however, the camera does use single-unit increments, like 7 or 11. the arrow key method of adjusting Tint goes in increments of 5 or 20, which for Tint is usually too broad of an adjustment.
sorry for the long post. anyone else having this problem? as someone who does a lot of toggling back-and-forth to compare things, i find this fairly small change in behavior incredibly disruptive.
my system:
late 2013, 15-inch rMBP; 2.3 GHz i7; 500gb SSD; 16gb RAM
OS 10.9.2 (not yet on 10.9.3 as there seem to be problems)
no Adobe CC items.

bob,
you are correct—what you said does work.
{for the sake of clarity and consistency, when i say double-click on the "slider", i mean on the value-marker, the triangular point that actually moves (or what ssprengel is calling the "slider-thumb/handle" if i'm understanding him correctly)—not the range on which it moves, nor the label to the left side of the range.}
but have i gone crazy?? has the behavior not changed at all?? i could have sworn that in the past, i was double-clicking (with or w/o shift key) on the value-marker of the slider, instead of on the label as you mention (although that instruction does sound familiar now, too). this is not a rare action for me, but something i've done countless times on the WB sliders, and also on the Black and White Mix sliders to return them to their auto value.
actually—now that i think about it, i do this action a ton on the HSL sliders, also: use the arrow keys (or Shift+arrow) to adjust HSL values, which go in increments of 5 (arrow) or 20 (shift+arrow). sometimes to return to zero i use the arrow keys again, but sometimes just double-click on the slider.
Or, if i want to see a very large, imprecise adjustment, i don't use the arrow keys but just click once towards the extemes of the range: +83 or -100 or whatever. and then to return to zero, i just double-click on that same spot—meaning on the slider/value-marker, wherever it happened to land on my first click.
however, in the last couple major releases (LR4 and now LR5), i've noticed that feature doesn't work quite as well as it used to. it used to be very easy to click once, get an extreme value, then very soon afterwards double-click and return to zero. you could do it easily, without even looking carefully at the sliders (so you could look instead at the picture changing). now, however, i find that i usually have to double-click two or three times before the slider responds and goes back to zero. sometimes i have to reposition the mouse very slightly and double-click again for that action to happen (and not because my mouse strayed from the slider).
i have noticed this to be true across many changing conditions:
major releases and smaller updates of LR;
different OS (10.6.8 snow leopard through 10.7, 10.8, and 10.9 mavericks);
different machines: 2007 MBP and late 2013 rMBP;
even different mice: used to have an old Kensington mouse; now using Logitech G500s, a fairly high-end gaming mouse (even though i don't do any gaming).
when i first noticed this less-responsive behavior, i thought it was due to my mouse and/or computer being old, maybe outdated. the kensington mouseworks software didn't really work, even on the older 2007 MBP. so i chalked it up to mouse issues. but it's exactly the same with my new, much more sophisticated mouse, whose software does work on my late 2013 rMBP.
(and now, with LR5.5, there's the issue i mentioned originally, where the first part of the double-click records a value shift before LR realizes i was actually double-clicking.)
why am i bothering to say all this??
first, it's an additional problem, but similar to what i originally posted about. second, it offers (at least some) support for my original idea—that in the past, i was, in fact, double-clicking on the slider itself, not on the label, to get auto or as-shot values.
does anyone else have any thoughts on this? am i the only one who "remembers" double-clicking on the slider, not the label, to get the auto or as-shot WB, or reset HSL sliders, or return to auto values of individual sliders in Black and White Mix?

Strange behavior (disappearing buttons, tabs, and more)

Very recently (within the past 3 days and long after installing 10.4.9) Safari on my iMac G5 has been exhibiting very strange behavior.
Some of the symptoms:
- crashes frequently for no apparent reason
- toolbar loses buttons and/or buttons are there but don't react to mouse clicks; sometimes a standard button, like forward, will simply disappear while backward remains
- text in URL field will become 'bolded' and sometimes difficult to read/blurry
- tabs often lose their dividing line boundaries
- auto entries usually not present
I have erased the preference list for Safari in my user library and repaired my permissions without any success.
Any suggestions?
Thank you very much for any help.

Hi
Please post a crash report - when Safari crashes, the "quit" panel has a "report" button. Select it, then copy/paste the entire contents to your reply.
While you are at it, try the site from another User Account. If you need to create a new account, please follow these steps:
Here is guidance from Apple on how to set up the account. You can ignore step 7 in the article.
Also, on the system preference>Accounts panel, click on "log-in" options. There, select "fast user switching". This allows you to go back and forth between user accounts via an icon in your Menu Bar at the top of the computer screen.
Log-on to the new account and start Safari. If Safari is stable in the new account, then your problem is specific to your regular user account. Otherwise, similar response means a system-wide problem.
Post back with results.

How to make panel collection with auto width and height in popup dialog ?

Hi,
I have ony af:popup in that I have added af:dialog. And in this af:dialog I have added af:table which is surrounded by af:panelCollection.
Means my popup structure is like as below
af:popup
af:dialog
af:panelCollection
af:table
If I set resize="on" in af:dialog then I can able to resize my popup dialog but the panelCollection inside the af:dialog is not become auto adjusted.
I am able to make panelCollection width auto adjusted by using AFStretchWidh style class but not able to adjust its height.
Hope you can understand my problem and pls try to provide me its solution if you have already implemented this.
Regards,
DevD

I believe you are using af:panelGroupLayout because there are some other components except af:panelCollection, so try this combination
<af:popup id="p1">
<af:dialog id="d2" resize="on" stretchChildren="first">
    <af:panelStretchLayout id="psl2">
      <f:facet name="bottom"/>
      <f:facet name="center">
        <af:panelCollection id="pc1">
          <f:facet name="menus"/>
          <f:facet name="toolbar"/>
          <f:facet name="statusbar"/>
          <af:table var="row" rowBandingInterval="0" id="t1">
            <af:column sortable="false" headerText="col1" id="c1">
              <af:outputText value="#{row.col1}" id="ot5"/>
            </af:column>
            <af:column sortable="false" headerText="col2" id="c3">
              <af:outputText value="#{row.col2}" id="ot4"/>
            </af:column>
            <af:column sortable="false" headerText="col3" id="c2">
              <af:outputText value="#{row.col3}" id="ot3"/>
            </af:column>
            <af:column sortable="false" headerText="col4" id="c4">
              <af:outputText value="#{row.col4}" id="ot2"/>
            </af:column>
            <af:column sortable="false" headerText="col5" id="c5">
              <af:outputText value="#{row.col5}" id="ot1"/>
            </af:column>
          </af:table>
        </af:panelCollection>
      </f:facet>
    </af:panelStretchLayout>
</af:dialog>
</af:popup>Put only af:panelCollection in CENTER facet of af:panelStretchLayout and use other facets of af:panelStretchLayout for other components.

Is there some place where I can submit a ticket ? Seems like FF limits DOM elements' width and height to 10,000,000px since it transforms this number into scientific notation. e.g. 10,000,000px becomes 1e+7px which obviously can't be interpreted. Cheers

I've reproduced this issue from FF 3.6.13 on windows XP and mac osx 10.6.8.
On FF 3.6.13 the number of pixels limit seems lower with exactly 8,388,607.

The 12" PB internals are a bit more complex, for PB's. If you don't want to replace the hard drive yourself or pay someone to install it, you could always get an external firewire hard drive, and use it to boot from and for general usage. Would have to be firewire, since the PB won't book from a USB device. One example of what you could get is a 160GB external hard drive: http://eshop.macsales.com/item/Other%20World%20Computing/MS4U5160GB8/ . All the choices with that case are listed here: http://eshop.macsales.com/shop/firewire/on-the-go
Have you called any Apple Authorized Service Providers to see what they would charge to install a drive for you? Whether you bought it or they supplied it? You can find a local one in the US at http://www.apple.com/buy/locator/service/

Disable the default "Start my camera" button for rtc WebcamPublisher

Hello,
I notice in the samples that WebCamera displays the cam. Is there an easy way of disabling the "Start my camera" button? I wish to control this from the app itself.
<rtc:WebCamera width="65%" height="396" id="webCamPub"/>
I notice in the WebCamera sample that it achieves removing the default "Start my camera" button, by assigning the rtc Webcamera a width and height of 1 and manipulating these through WebCamPublisher class, but I do not see anywhere a "button" = disabled or something similar .

Ok thanks, overriding the addStartStopBtn function fortunately was a piece of cake for the WebCamera class, and that was all I needed.
I notice WebCamera is extremely advanced compared to the simpler webcamsuvscriber stuff.
I try to build on adobe grown material so I can avoid high maintenance costs down the road

Visual Studio 2013 slows down + crashes when using Source Control features.

I have spent two full days trying to resolve this issue but no luck so here we go,
I have created a project using Visual Studio Team Foundation Server plug-in in the past. Later on I switched to
Microsoft Git Provider.
Now when I connect to that project in the Team Explorer and double click on the solution to work on it locally it somehow changes the plug in to Microsoft Git Provider automatically and of course I can't
Commit/Commit and Push since I receive following error in the Team Explorer,
An error occurred. Detailed message: Failed to open directory 'C:/Users/.../AppData/Local/Application Data/'
Manually changing the plug-in to the Visual Studio Team Foundation Server
results in a broken Team Explorer as below,
With Settings leading to an empty pane, and also a warning in the Team Explorer's Changes page telling me the message below if I click on Pending Changes...
Microsoft Git Provider is not the current Source Control plug-in. Change Plug-in
And manually selecting the solution from Solution Explorer, right click and
Add Solution to Source Control, leads to never ending hour glass and (Not responding) visual studio.
New Projects
Creating a new project is straight forward, unless I "Add to Source Control" is checked. If so, again never ending process if Microsoft TFS plug-in is selected in the tools and eventually me Ending the Visual Studio task. And a VERY long process
(40+ mins) if I have chosen Microsoft Git but that finishes successfully rather.
New TFS project from Team Explorer
If I create a new project in my Online Web Studio
Click on Open with Visual Studio Link => Opens and connects to a my newly created TFS in team explorer.
Clicking new in Team Explorer under Solutions to create a new solution and bind it to this Repo
leads to straight crash of Visual Studio and restarting attempt of VS.
So I really can't use Source Control from visual studio other than cloning GitHub's existing repo's on Visual Studio and Committing my current Microsoft Git managed projects.
I have attempted
Repairing Visual Studio (no luck in results)
Devenv.exe /setup (no luck)
Trying to scrap the SCC info on my solution then at least it won't get picked up by source control then I can Check it in as a new project. (no luck and the solution picks the Microsoft Git upon opening it by clicking on the .sln file.) I have followed
these steps in this stack overflow answer.
And lots of mucking around like removing my workspaces almost Thousand times and putting them back, binding and etc.
I am really stuck on this and it's holding me back from staring a new project (which is problematic using Adding to Source Control) and unfortunately is dependent on the old project (which is developed under Visual Studio Team Foundation Server Plug-in which
is throwing tantrums)
Would like to hear you pro-s input on this
Using
Visual Studio 2013 Community edition (recently switched from Pro to Express to Community)
Windows 7 (64-bit)
Git tools
Git windows installation
Nuget Package manager
Visual Studio Log File
http://filesave.me/file/50620/log-txt.html
Mehradzie

Hi Mehradzie,
Based on the description, seems you're working with Git team project in Visual Studio Online(formerly Team Foundation Service). I'd like to know whether you mean Visual Studio Git command tool as the plug-in, and if you're trying to create solutions/projects
with Visual Studio and add them to the created Git team project.
From the screenshot, you're not connect to the Git team project by using Team Explorer. To work with Git team project locally, you can follow the instructions as below:
Connect to Git team project by using Team Explorer, after that you might install Git tools if you connect to the team project for the first time
Clone the remote Git repository to a local git repository and set the path to local git repository
Create a solution and select Git source control, also saved to the local path of the local git repository
Select your branch, and then click "Changes" and Commit the changes
Click "unsynced commits" and push the commit to remote git repository
You can also refer to the links below for more information about getting started with Git in Visual Studio Online.
http://www.visualstudio.com/en-us/get-started/share-your-code-in-git-vs.aspx
http://blogs.msdn.com/b/visualstudioalm/archive/2013/01/30/getting-started-with-git-in-visual-studio-and-team-foundation-service.aspx
If you still have any other concerns, please elaborate more details about your scenario. Thanks for your understanding.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Tab Bar Control and the Default "More" Behavior

I've got a client who wants an app with 8 tabs. The only problem is that they don't like the default "more" behavior with the tableviewcontroller containing the extra tab content. What they want is to hit "more" to see the next four tabs replace the first four and then to toggle back if it's hit again.
There are a few ways to do this, I guess. I could build a second viewcontroller/tabcontroller that comes on or leaves when "more" is touched. Is there a surer way of doing this? I'm sure I'm missing something basic, but I've googled my brains out on this one and just can't see it.

You could use one TabbarController with 8 ViewControllers, and rotate them when the More tab is tapped:
- (BOOL)tabBarController:(UITabBarController *)tbc shouldSelectViewController:(UIViewController *)vc {
if (vc == tbc.moreNavigationController) {
NSMutableArray *newVCs = [[NSMutableArray arrayWithCapacity:8] retain];
for (int i = 0; i < 8; i++) {
[newVCs addObject:[tbc.viewControllers objectAtIndex:(i + 4) % 8]];
tbc.viewControllers = newVCs;
[newVCs release];
return NO;
} else {
return YES;

Auto Run ignores URL parameters and uses Defaults on first run

We have BI Publisher 11g standalone (not OBIEE).
We have a suite of BI Publisher reports, all set up on data sets with default parameters.
All reports have Auto Run enabled and caching disabled.
The reports are run from a Flex UI application using a URL i.e. URLVariables and URLRequest and navigateToURL.
The required parameters for any report are read from BI Publisher using the web services, then the user makes their selections in our custom UI.
We use:
                         urlVariables['_xpf'] = null;
                         urlVariables['_xpt'] = 0;
                         urlVariables['_xf'] = 'html';
                         urlVariables['_xmode'] = 1;
The first time any user runs any report in the application the report is generated but with the default parameters NOT their selected values, and it displays the parameter controls when the settings as per above say it should NOT.
Any report generation after that is fine - it runs with the user's nominated parameters values, and it does not display the parameter controls.
Originally we thought it might be caching so along with all report caching settings being disabled, we introduced a parameter to force the uniqueness of each report URL i.e.
                         urlVariables['noCache'] = new Date().getTime();
In Safari, if we Reset Safari then restart the app in the same browser window we can reproduce the problem.
Any suggestions please?
Thanks

I'm not sure where the "Enable Document Cache" setting is?
All reports have caching disabled - so for each report in its Report Properties, all items on the Caching tab are checked off.
i.e.
Enable Data Caching - off
User Level - off
Document Caching - off

How to Control default Styles(Font,BGColor,Size) for WPC Objects.

Hi All,
This is Ganesh, Current i am working on Content Migration Using WPC.Now My Question, while we are creating the Site Content using WPC(Like Articles, Paragraph's, etc...), while we are typing the content for Article, its showing in one font, after creation of article,while we are previewing of the Article , its showing in Blue Color Letter's and Shade Blue back ground and also Coming font big in size.
If i am creating the paragraph, while we are previewing the its Displaying in Black Color.
From where the details of font, size and back ground colors are coming in WPC objects.and if they have to modified, how can it be done?
Where We can Control the Default Styles for WPC Content Creation Objects.If Possible how to modify?
Please provide some valuble inputs for my Query???
Thanks in Advance
Krishna Ganesh

Ganesh,
You are absolutely right. If you modify the xml, xsl and css files supplied by the standard SAP it will affect all the users. Please note that whenever you need to modify the css, you need to do the same in /etc/wpceditor/css/runtime folder. Modification of the css in /etc/wpceditor/css/designtime folder is not of any use.
If you do not want the changes made to the style to affect all other users, it is always wiser and recommended to create your own custom webform. Some webforms like Article, Link List, banner, teaser etc are provided by SAP. If you want to create your own webform and apply the style to that webform alone then you need to follow the process of creating custom webforms in WPC.
In order to change the style you need to understand a bit of XML and XSL transformation.
You can refer to the following sdn help for the same - http://help.sap.com/saphelp_nw70/helpdata/en/45/599b78b0aa3bdde10000000a1553f7/frameset.htm
Hope it helps. Let me know if you need any further clarification.

Default focus behavior in Swing

I have a JTabbedPane wherein every tab has a variety of fields, including buttons, text areas, text fields, tables, and so on. I wanted to tweak the default focus behavior such that the first text field or the first text area has the focus.
I used requestFocusInWindow() to set the focus on the first text field I get. This, however, was being overriden at a later stage (I am working on a vast code) and the first component inside a tab is getting the focus.
Is there any means to override the default focus behavior? I tried writing my own FocusTraversalPolicy but found that that is never used. How does the default focus behavior work? Does it set the focus on the first field it gets or what? And where can I find the code for the same?

I used requestFocusInWindow() to set the focus on the first text field I get. The requestFocusInWindow() method only works when the GUI is already visible. So I would suggest that you add a ChangeListener to the tabbed pane and add your code to set the focus every time the tab is changed.
For a slightly different approach the code in this posting will remember the last field for each tab that had focus and reset focus to that field when the tab is changed. The code is not completely off topic since it shows how to use a ChangeListener:
http://forum.java.sun.com/thread.jspa?forumID=57&threadID=570369

Alsa: how to controll the auto mute feature?

Hi,
I have a slight problem with my laptop.
I have a headphone jack, a analogue volume control wheel and my normal speakers.
What I like to have is this:
Plug in headphones => sound only from headphones
No headphones plugged => sound from main speakers (I do not care if sound is still put onto the headphone jack as I would not here it one way or the other)
Right now, this is not working out of the box.
Plugging in my headphones mutes the speakers, great, but it does not unmute my headphones so I hear nothing until I go into alsamixer and unmute my headphones.
This would not be a problem but once I unplug my headphones, alsa mutes them. Ergo, everytime I unplug and plug my headphone I have to unmute them in the alsa mixer.
Can someone tell me where I can controll this behaviour to fix this?
I have seen multiple entries for pulseaudio (which I am not usign right now) or references to a auto-mute button in alsamixer which I do not seem to have in mine.
With best regards,
p90

@nomorewindows See if the same happens with power_save and power_save_controller parameters set to 0.
@p90 did you try replugging twice or more times? One more thing you can try is to run 'alsactl store' before plugging headphones in with speakers outputting sound, then after unplugging run 'alsactl restore'. You can use -f switch, see the manual.

ChildWindow control default style and template - VS2013 Silverlight5

Is there a updated version of ChildWindow control default style for VS2013 SIlverlight5. I am customizing the style to remove borders and the default style
that I found on MSDN library seems old (2012). When I apply this style, the child window is placed at the top left corner (bug!?) instead of center.
Could some one provide the latest version of the style template.
Thanks in advance.
Salini

This fixed the border and position issue I have earlier. Thank you for all your responses.
<Style x:Key="ChildWindowStyle" TargetType="controls:ChildWindow">
<Setter Property="IsTabStop" Value="false"/>
<Setter Property="TabNavigation" Value="Cycle"/>
<Setter Property="HorizontalAlignment" Value="Center"/>
<Setter Property="VerticalAlignment" Value="Center"/>
<Setter Property="HorizontalContentAlignment" Value="Stretch"/>
<Setter Property="VerticalContentAlignment" Value="Stretch"/>
<Setter Property="BorderThickness" Value="1"/>
<Setter Property="BorderBrush">
<Setter.Value>
<LinearGradientBrush EndPoint="0.5,1" StartPoint="0.5,0">
<GradientStop Color="#FFA3AEB9" Offset="0"/>
<GradientStop Color="#FF8399A9" Offset="0.375"/>
<GradientStop Color="#FF718597" Offset="0.375"/>
<GradientStop Color="#FF617584" Offset="1"/>
</LinearGradientBrush>
</Setter.Value>
</Setter>
<Setter Property="OverlayBrush" Value="#7F000000"/>
<Setter Property="OverlayOpacity" Value="1"/>
<Setter Property="Template">
<Setter.Value>
<ControlTemplate TargetType="controls:ChildWindow">
<Grid x:Name="Root">
<Grid.Resources>
<Style x:Key="ButtonStyle" TargetType="Button">
<Setter Property="Background" Value="#FF1F3B53"/>
<Setter Property="Foreground" Value="#FF000000"/>
<Setter Property="Padding" Value="3"/>
<Setter Property="BorderThickness" Value="1"/>
<Setter Property="BorderBrush">
<Setter.Value>
<LinearGradientBrush EndPoint="0.5,1" StartPoint="0.5,0">
<GradientStop Color="#FFA3AEB9" Offset="0"/>
<GradientStop Color="#FF8399A9" Offset="0.375"/>
<GradientStop Color="#FF718597" Offset="0.375"/>
<GradientStop Color="#FF617584" Offset="1"/>
</LinearGradientBrush>
</Setter.Value>
</Setter>
<Setter Property="Template">
<Setter.Value>
<ControlTemplate TargetType="Button">
<Grid x:Name="grid" Background="#02FFFFFF" HorizontalAlignment="Center"
Height="14" VerticalAlignment="Center" Width="15">
<VisualStateManager.VisualStateGroups>
<VisualStateGroup x:Name="CommonStates">
<VisualState x:Name="Normal"/>
<VisualState x:Name="MouseOver">
<Storyboard>
<ObjectAnimationUsingKeyFrames
Storyboard.TargetProperty="Visibility" Storyboard.TargetName="X_Fuzz2">
<DiscreteObjectKeyFrame
KeyTime="0" Value="Visible"/>
</ObjectAnimationUsingKeyFrames>
<ObjectAnimationUsingKeyFrames
Storyboard.TargetProperty="Visibility" Storyboard.TargetName="X_Fuzz1">
<DiscreteObjectKeyFrame
KeyTime="0" Value="Visible"/>
</ObjectAnimationUsingKeyFrames>
<ObjectAnimationUsingKeyFrames
Storyboard.TargetProperty="Visibility" Storyboard.TargetName="X_Fuzz0">
<DiscreteObjectKeyFrame
KeyTime="0" Value="Visible"/>
</ObjectAnimationUsingKeyFrames>
<DoubleAnimation
Duration="0" To="0.95" Storyboard.TargetProperty="Opacity" Storyboard.TargetName="X"/>
</Storyboard>
</VisualState>
<VisualState x:Name="Pressed">
<Storyboard>
<DoubleAnimation
Duration="0" To="0.85" Storyboard.TargetProperty="Opacity" Storyboard.TargetName="X"/>
<ObjectAnimationUsingKeyFrames
Storyboard.TargetProperty="Visibility" Storyboard.TargetName="X_Fuzz2">
<DiscreteObjectKeyFrame
KeyTime="0" Value="Visible"/>
</ObjectAnimationUsingKeyFrames>
<ObjectAnimationUsingKeyFrames
Storyboard.TargetProperty="Visibility" Storyboard.TargetName="X_Fuzz1">
<DiscreteObjectKeyFrame
KeyTime="0" Value="Visible"/>
</ObjectAnimationUsingKeyFrames>
<ObjectAnimationUsingKeyFrames
Storyboard.TargetProperty="Visibility" Storyboard.TargetName="X_Fuzz0">
<DiscreteObjectKeyFrame
KeyTime="0" Value="Visible"/>
</ObjectAnimationUsingKeyFrames>
</Storyboard>
</VisualState>
<VisualState x:Name="Disabled">
<Storyboard>
<DoubleAnimation
Duration="0" To="0.5" Storyboard.TargetProperty="Opacity" Storyboard.TargetName="X"/>
</Storyboard>
</VisualState>
</VisualStateGroup>
</VisualStateManager.VisualStateGroups>
<Path x:Name="X_Fuzz2" Data="F1 M 6.742676,3.852539 L 9.110840,1.559570
L 8.910645,0.500000 L 6.838379,0.500000 L 4.902832,2.435547 L 2.967285,0.500000 L 0.895020,0.500000 L 0.694824,1.559570 L 3.062988,3.852539 L 0.527832,6.351563 L 0.689941,7.600586 L 2.967285,7.600586 L 4.897949,5.575195 L 6.854004,7.600586 L 9.115723,7.600586
L 9.277832,6.351563 L 6.742676,3.852539 Z" Fill="#14C51900" HorizontalAlignment="Center" Height="8" Margin="0,-1,0,0" Opacity="1" RenderTransformOrigin="0.5,0.5" Stretch="Fill" Stroke="#14C51900"
Visibility="Collapsed" VerticalAlignment="Center" Width="9">
<Path.RenderTransform>
<TransformGroup>
<ScaleTransform ScaleY="1.3"
ScaleX="1.3"/>
</TransformGroup>
</Path.RenderTransform>
</Path>
<Path x:Name="X_Fuzz1" Data="F1 M 6.742676,3.852539 L 9.110840,1.559570
L 8.910645,0.500000 L 6.838379,0.500000 L 4.902832,2.435547 L 2.967285,0.500000 L 0.895020,0.500000 L 0.694824,1.559570 L 3.062988,3.852539 L 0.527832,6.351563 L 0.689941,7.600586 L 2.967285,7.600586 L 4.897949,5.575195 L 6.854004,7.600586 L 9.115723,7.600586
L 9.277832,6.351563 L 6.742676,3.852539 Z" Fill="#1EC51900" HorizontalAlignment="Center" Height="8" Margin="0,-1,0,0" Opacity="1" RenderTransformOrigin="0.5,0.5" Stretch="Fill" Stroke="#1EC51900"
Visibility="Collapsed" VerticalAlignment="Center" Width="9">
<Path.RenderTransform>
<TransformGroup>
<ScaleTransform ScaleY="1.1"
ScaleX="1.1"/>
</TransformGroup>
</Path.RenderTransform>
</Path>
<Path x:Name="X_Fuzz0" Data="F1 M 6.742676,3.852539 L 9.110840,1.559570
L 8.910645,0.500000 L 6.838379,0.500000 L 4.902832,2.435547 L 2.967285,0.500000 L 0.895020,0.500000 L 0.694824,1.559570 L 3.062988,3.852539 L 0.527832,6.351563 L 0.689941,7.600586 L 2.967285,7.600586 L 4.897949,5.575195 L 6.854004,7.600586 L 9.115723,7.600586
L 9.277832,6.351563 L 6.742676,3.852539 Z" Fill="#FFC51900" HorizontalAlignment="Center" Height="8" Margin="0,-1,0,0" Opacity="1" Stretch="Fill" Stroke="#FFC51900" Visibility="Collapsed"
VerticalAlignment="Center" Width="9"/>
<Path x:Name="X" Data="F1 M 6.742676,3.852539 L 9.110840,1.559570
L 8.910645,0.500000 L 6.838379,0.500000 L 4.902832,2.435547 L 2.967285,0.500000 L 0.895020,0.500000 L 0.694824,1.559570 L 3.062988,3.852539 L 0.527832,6.351563 L 0.689941,7.600586 L 2.967285,7.600586 L 4.897949,5.575195 L 6.854004,7.600586 L 9.115723,7.600586
L 9.277832,6.351563 L 6.742676,3.852539 Z" Fill="#FFFFFFFF" HorizontalAlignment="Center" Height="8" Margin="0,-1,0,0" Opacity="0.7" Stretch="Fill" VerticalAlignment="Center" Width="9">
<Path.Stroke>
<LinearGradientBrush EndPoint="0.5,1"
StartPoint="0.5,0">
<GradientStop Color="#FF313131"
Offset="1"/>
<GradientStop Color="#FF8E9092"
Offset="0"/>
</LinearGradientBrush>
</Path.Stroke>
</Path>
</Grid>
</ControlTemplate>
</Setter.Value>
</Setter>
</Style>
</Grid.Resources>
<VisualStateManager.VisualStateGroups>
<VisualStateGroup x:Name="WindowStates">
<VisualState x:Name="Open">
<Storyboard>
<DoubleAnimationUsingKeyFrames BeginTime="0" Storyboard.TargetProperty="Opacity"
Storyboard.TargetName="Overlay">
<EasingDoubleKeyFrame KeyTime="0" Value="0"/>
<EasingDoubleKeyFrame KeyTime="00:00:00.3" Value="1"/>
</DoubleAnimationUsingKeyFrames>
<DoubleAnimationUsingKeyFrames BeginTime="0" Storyboard.TargetProperty="(RenderTransform).(Children)[0].ScaleX"
Storyboard.TargetName="ContentRoot">
<SplineDoubleKeyFrame KeyTime="0" Value="0"/>
<SplineDoubleKeyFrame KeyTime="00:00:00.25" Value="0"/>
<SplineDoubleKeyFrame KeyTime="00:00:00.4" Value="1"/>
<SplineDoubleKeyFrame KeySpline="0,0,0.5,1" KeyTime="00:00:00.45"
Value="1.05"/>
<SplineDoubleKeyFrame KeyTime="00:00:00.55" Value="1"/>
</DoubleAnimationUsingKeyFrames>
<DoubleAnimationUsingKeyFrames BeginTime="0" Storyboard.TargetProperty="(RenderTransform).(Children)[0].ScaleY"
Storyboard.TargetName="ContentRoot">
<SplineDoubleKeyFrame KeyTime="0" Value="0"/>
<SplineDoubleKeyFrame KeyTime="00:00:00.25" Value="0"/>
<SplineDoubleKeyFrame KeyTime="00:00:00.4" Value="1"/>
<SplineDoubleKeyFrame KeySpline="0,0,0.5,1" KeyTime="00:00:00.45"
Value="1.05"/>
<SplineDoubleKeyFrame KeyTime="00:00:00.55" Value="1"/>
</DoubleAnimationUsingKeyFrames>
</Storyboard>
</VisualState>
<VisualState x:Name="Closed">
<Storyboard>
<DoubleAnimationUsingKeyFrames BeginTime="0" Storyboard.TargetProperty="Opacity"
Storyboard.TargetName="Overlay">
<EasingDoubleKeyFrame KeyTime="0" Value="1"/>
<EasingDoubleKeyFrame KeyTime="00:00:00.3" Value="0"/>
</DoubleAnimationUsingKeyFrames>
<DoubleAnimationUsingKeyFrames BeginTime="0" Storyboard.TargetProperty="(RenderTransform).(Children)[0].ScaleX"
Storyboard.TargetName="ContentRoot">
<SplineDoubleKeyFrame KeyTime="00:00:00.2" Value="1"/>
<SplineDoubleKeyFrame KeyTime="00:00:00.25" Value="1.05"/>
<SplineDoubleKeyFrame KeyTime="00:00:00.45" Value="0"/>
</DoubleAnimationUsingKeyFrames>
<DoubleAnimationUsingKeyFrames BeginTime="0" Storyboard.TargetProperty="(RenderTransform).(Children)[0].ScaleY"
Storyboard.TargetName="ContentRoot">
<SplineDoubleKeyFrame KeyTime="00:00:00.2" Value="1"/>
<SplineDoubleKeyFrame KeyTime="00:00:00.25" Value="1.05"/>
<SplineDoubleKeyFrame KeyTime="00:00:00.45" Value="0"/>
</DoubleAnimationUsingKeyFrames>
</Storyboard>
</VisualState>
</VisualStateGroup>
</VisualStateManager.VisualStateGroups>
<Grid x:Name="Overlay" Background="{TemplateBinding OverlayBrush}" HorizontalAlignment="Stretch" Margin="0" Opacity="{TemplateBinding
OverlayOpacity}" VerticalAlignment="Top"/>
<Grid x:Name="ContentRoot" HorizontalAlignment="{TemplateBinding HorizontalAlignment}" Height="{TemplateBinding Height}" RenderTransformOrigin="0.5,0.5"
VerticalAlignment="{TemplateBinding VerticalAlignment}" Width="{TemplateBinding Width}">
<Grid.RenderTransform>
<TransformGroup>
<ScaleTransform/>
<SkewTransform/>
<RotateTransform/>
<TranslateTransform/>
</TransformGroup>
</Grid.RenderTransform>
<Border BorderBrush="{TemplateBinding BorderBrush}" BorderThickness="{TemplateBinding BorderThickness}" Background="#FFFFFFFF"
CornerRadius="2">
<Border CornerRadius="1.5" Margin="1">
<Border.Background>
<LinearGradientBrush EndPoint="0.5,1" StartPoint="0.5,0">
<GradientStop Color="#FFE5E8EB" Offset="1"/>
<GradientStop Color="#FFF6F8F9" Offset="0"/>
</LinearGradientBrush>
</Border.Background>
<Grid>
<Grid.RowDefinitions>
<RowDefinition Height="Auto"/>
<RowDefinition/>
</Grid.RowDefinitions>
<Border x:Name="Chrome" BorderBrush="#FFFFFFFF" BorderThickness="0,0,0,1"
Width="Auto">
<Border.Background>
<LinearGradientBrush EndPoint="0.5,0.528" StartPoint="0.5,0">
<GradientStop Color="#FFE5E8EB" Offset="1"/>
<GradientStop Color="#FFFEFEFE" Offset="0"/>
</LinearGradientBrush>
</Border.Background>
<Grid Height="Auto" Width="Auto">
<Grid.ColumnDefinitions>
<ColumnDefinition/>
<ColumnDefinition Width="30"/>
</Grid.ColumnDefinitions>
<ContentControl Content="{TemplateBinding Title}" FontWeight="Bold"
HorizontalAlignment="Stretch" IsTabStop="False" Margin="6,0,6,0" VerticalAlignment="Center"/>
<Button x:Name="CloseButton" Grid.Column="1" HorizontalAlignment="Center"
Height="14" IsTabStop="False" Style="{StaticResource ButtonStyle}" VerticalAlignment="Center" Width="15"/>
</Grid>
</Border>
<Border Grid.Row="1">
<ContentPresenter x:Name="ContentPresenter" ContentTemplate="{TemplateBinding
ContentTemplate}" Content="{TemplateBinding Content}" HorizontalAlignment="{TemplateBinding HorizontalContentAlignment}" VerticalAlignment="{TemplateBinding VerticalContentAlignment}"/>
</Border>
</Grid>
</Border>
</Border>
</Grid>
</Grid>
</ControlTemplate>
</Setter.Value>
</Setter>
</Style>

Extending default ViewCriteriaAdapter behavior

hi
I am looking for an easy way to change the ViewCriteria behavior for one (type of) field and keep the default behavior for the other fields.
I would like this
vMyViewCriteriaRow.setAttribute("REG_DATE", "05-2005");to result in a where clause fragment like
(REG_DATE >= TO_DATE('01-05-2005', 'DD-MM-YYYY') AND REG_DATE < TO_DATE('01-06-2005', 'DD-MM-YYYY'))or like
(REG_DATE BETWEEN TO_DATE('01-05-2005', 'DD-MM-YYYY') AND (TO_DATE('01-06-2005', 'DD-MM-YYYY') - 1))or something else, for whatever reason
I've read
"Implementing a View Criteria Adapter to Customize Query By Example Functionality"
http://radio.weblogs.com/0118231/stories/2003/07/11/implementingAViewCriteriaAdapterToCustomizeQueryByExampleFunctionality.html
but it doesn't describe how to keep some of the default behavior.
My solution (for now) is based on this article though:
public class DateViewCriteriaAdapter extends OracleSQLBuilderImpl
     public String getViewCriteriaClause(ViewObject pViewObject,
          ViewCriteria pViewCriteria)
          if (pViewCriteria == null || pViewCriteria.size() == 0)
               return null;
          ViewCriteria vModifiedViewCriteria = pViewCriteria;
          StringBuffer vCustomFragment = new StringBuffer();
          if (pViewCriteria.size() == 1)
               vModifiedViewCriteria = pViewObject.createViewCriteria();
               ViewCriteriaRow vModifiedVCRow =
                    vModifiedViewCriteria.createViewCriteriaRow();
               vModifiedViewCriteria.add(vModifiedVCRow);
               ViewCriteriaRow vVCRow = (ViewCriteriaRow)pViewCriteria.first();
               StructureDef vStructureDef = vVCRow.getStructureDef();
               AttributeDef[] vAttributeDefs = vStructureDef.getAttributeDefs();
               for (int i = 0, vLength = vAttributeDefs.length; i < vLength; i++)
                    String vCriteriaAttVal = (String)vVCRow.getAttribute(i);
                    if (vCriteriaAttVal != null && !"".equals(vCriteriaAttVal))
                         String vAttributeFragment = getWhereClauseFragmentForAttribute(
                              vAttributeDefs, vCriteriaAttVal);
                         if (vAttributeFragment != null)
                              appendFragment(vCustomFragment, vAttributeFragment);
                         else
                              vModifiedVCRow.setAttribute(i, vCriteriaAttVal);
          String vDefaultFragment = super.getViewCriteriaClause(
               pViewObject, vModifiedViewCriteria);
          appendFragment(vCustomFragment, vDefaultFragment);
          return "( " + vCustomFragment.toString() + " )";
     private String getWhereClauseFragmentForAttribute(AttributeDef pAttributeDef,
          String pCriteriaAttVal)
          String vCriteriaAttVal = pCriteriaAttVal.trim();
          if (pAttributeDef.getJavaType() == oracle.jbo.domain.Date.class)
          return null;
I'm not really happy with this solution because:
(1) It extends OracleSQLBuilderImpl which extends BaseSQLBuilderImpl for which the API documentation states "Internal: Applications should not use this interface.", so I'm not sure if I'm supposed to extend OracleSQLBuilderImpl.
(2) It only works for ViewCriteria with one ViewCriteriaRow. As this solution depends on a call to super.getViewCriteriaClause(), there is no way to correctly "AND and OR" all (custom and default) fragments together.
my question:
Is this the way to go, or should I use another aproach?
thanks
Jan Vervecken

Thanks for your reply Steve.
It took me a while, but I've been able to get an enhancement request logged for this, see metalink.oracle.com (search bugs for this number):
4651343 : EXTENDING DEFAULT VIEWCRITERIAADAPTER BEHAVIOR
Although I don't know about the other values the "Desirability" attribute of this enhancement request can have, I don't agree with "Somewhat desirable feature".
Because it enables both "productivity" and "choice", I believe it deserves a stronger desirability-status.
greetings
Jan Vervecken

Where do I control default Auto behavior of Button.Width and .Height in Visual Basic 2013 designer?

Similar Messages

Maybe you are looking for