The book that I purchased to help with my SSIS understanding seems to have glossed over this, and I wanted to know exactly what is the method to turn on FastParse in SSIS?
To set fast parse (from here)
Right-click the Flat File source or Data Conversion transformation, and then click Show Advanced Editor.
In the Advanced Editor dialog box, click the Input and Output Properties tab.
In the Inputs and Outputs pane, click the column for which you want to enable fast parse.
In the Properties window, expand the Custom Properties node, and then set the FastParse property to True.
Click OK.
Related
I use STM32CubeIDE version 1.6.1, and have noticed that CubeMX outputs formatted code (e.g. indented with 2 spaces). I would like to reapply this source code formatting manually (that is, manually trigger the source code formatting on selected files).
I have found this post: https://www.openstm32.org/forumthread6435 , which mentions:
go the preferences dialog and select C/C++ > Code Style > Formatter
click on “Edit...” change the tab size field. close the preferences
Then, select all the project you want to apply it, click right and select “Source > Format”
So, I'm not 100% sure the above quote refers to STM32CubeIDE, however, the first part is still there, in Window/Preferences I can get to this:
However, I cannot see how to trigger this source code formatting manually, on selected files. For instance, https://dvteclipse.com/documentation/e/Format_Multiple_Files.html for Eclipse (that STM32CubeIDE is built upon), mentions that by right-clicking source files, one can call the command "Format Source Files"; however, when I click my main.c in the STM32CubeIDE Project Explorer, I cannot see anything like that:
So, is there a way to manually trigger automatic source code formatting on selected (single or multiple) source code files in STM32CubeIDE?
Got it, finally - when you right-click the Core node, or any of its children, in Project Explorer in STM32CubeIDE, you get a "Source >" entry in the right-click context menu, which has only one child, "Format":
.
In VB6, the dropdown in the IDE shown above wasn't categorized.
I could easily browse "ucBoardGrid"'s events and properties as they were all shown in the same dropdown menu.
While VS2017 tries to organize things for me, I feel that it's mostly much more time-taking to browse where I want to:
First I need to select the "main category" in the left dropdown menu, then I can view the methods / events / properties in the right dropdown menu.
Is there a way to disable this categorization? I would like everything to be shown in a single dropdown list right away.
I fondly remember the old VB6 menu's just as you've explained.
I would like everything to be shown in a single dropdown list right away.
I doubt you can remove the categorization, however I have something far more amazing. These days I find myself using Ctrl+T.
The new Go to All window in Visual Studio 2017 lets you navigate directly to any file, type, member, line or symbol by typing a search query:
The main difference from the Navigate To window (existed since Visual Studio 2010) is that now you can easily limit search results to files, types, members or symbols clicking on the corresponding toolbar button. Alternatively, you can type the special character and space before the search query:
Works for Files (f), Types (t), Members (m), Symbols (#) and Lines (:), e.g. f stac for file paths containing stac
Edit: Apart from Ctrl+T, I typically use F12 to goto definition. Then I use Ctrl+ minus key to go back, and back, F12 forward, and back, again. It's the fastest I've found.
I'm also a fan while debugging to pull up Ctrl+Alt+c the call stack, up/down arrow keys while focus is on CallStack window.
F12 & Ctrl+- is the key, anything else Ctrl+T.
Can't find any references for how to add a data layer into a custom toolbox that I made in ArcMap via a dropdown menu instead of navigating to the file location.
The first picture is what the input for my tool lookslike, and the second is a screen shot of the Clip tool which has the dropdown options.
You have not set the parameter type in the script input parameters. This cannot be controlled in the script that you created, but has to be done in the tool (within ArcMap).
For this specific case, I believe Feature Class is the parameter type that you want (if not, Feature Layer -- I honestly haven't done this in ages, and there are quite a few options!)
You can also set options such as whether or not the parameter is required.
See Esri help pages for full details: Setting script tool parameters and Understanding script tool parameters.
For each model element, there is the option in EA 10 to create internal requirements, constraints and scenarios. All of them end up in reports if you use the pre-defined Basic Template.
However, if you select "structured specification" instead of the default "description" text field for a scenario, then I end up with the steps of the structured specification being ignored in the report output.
How can I have them included in reports?
It sounds like you need to create your own reporting template. This may seem a bit daunting first time out and the template editor is pretty ornery, but luckily you can use an existing template as a starting point.
Hit F8 to bring up the Generate Documentation dialog, then select the Templates tab. Click New, specify a name and select a template you like to be copied. Don't bother with a template group, and leave the fragment checkbox unchecked.
In the editor, scroll down about halfway (assuming you selected to copy the Basic template) and locate the yellow scenario > tag.
Now in the checkbox tree on the left, scroll down do Package - Element - Scenario. Note that Scenario is checked, but Structured Scenarios is not. Check it.
In the editor, note the new structured scenarios > tag. Remove the right-click-to-insert text, then right-click and select Insert Field, then State etc.
It's more than a little fiddly, but if the Basic template is good enough to begin with you should be able to add the structured scenarios with a minimum of effort.
For more information, see the help file under Reporting - RTF Documents. Note that the individual fields aren't listed in the help file, you need to open up the template editor to see what specific information you can extract to your report.
I have modified EditForm.aspx of a list in SharePoint 2010. I need to launch the dialog window (that's what EditForm.aspx seems to be launched as) maximized, but I haven't been able to find the correct setting to tweak.
A quick web search suggests to use the showMaximized:true style setting, but I am unable to find the element in EditForm.aspx to apply this attribute to.
If you want to remove ALL dialogs from a list, go to:
list settings -> advanced -> dialog -> turn them off
But if you just want to change the edit button, you will probably have to create a new edit <CustomAction> that uses javascript, see this example:
http://www.chakkaradeep.com/post/Using-the-SharePoint-2010-Modal-Dialog.aspx
Its for a different button, but you should get the idea.
And then you will need to build a <HideCustomAction> to hide the original edit button
Check this : http://www.wawawum.com/blog/post.aspx?id=66a5aed2-f530-4687-bd42-1ef0fb379544
Add a Content Editor WebPart to your EditForm, then put the code found in this blog to maximize the Dialog when opening it.
Works very well for me.