Oracle adf 12c Load more scroll new policy - oracle-adf

hi I've added the new scroll load more policy onto my table grid and it works just fine. But after i have deleted a column from the grid it doesn't show the load more scroll anymore, why is this?

But after i have deleted a column from the grid
Probably you have deleted more than necessary.
If you use a version control, you should revert to your previous state (before removing), make sure code works and remove the column again.
You should always compare the changes you made against the one from version control, to be sure you change only what you are supposed to.
Learning using version control is an important element ADF study.

Related

TinyMCE table not working/loading correctly on material-ui Modal

I'm using the currrent last version of TinyMCE, and i'm having a struggle with the table plugin. On my project i import the editor in two instances, one on a separate page dedicated only to the editor, and a second one that is being displayed on a material-ui Modal, to make some minor changes over the document.
What happens is that the table plugin seems not to be loading correctly, since i can add whatever columns and rows i want, but they appeared to be disabled to only add a 1x1 table.
Table grid
Also... and this is the one that worries me most. Is that the table properties when i focus the table, are not displaying the actual properties window/popup.
TableProps on focus
And if i decided to access those properties by right clicking the table, although the properties windows show up, i cannot change anything there, all properties seems to be disabled.
Properties disabled
If anyone have solution to fix this issue it would really help a lot!
Thank you by advance!
Material UI by default blocks the focus from leaving the modal dialog as noted here: https://mui.com/components/modal/#focus-trap. This then prevents you from interacting with any popups TinyMCE creates. So to fix this you should be able to prevent the focus trap behaviour by adding either disableEnforceFocus or disableEnforceFocus={true}, as noted in the Material UI docs.

SSRS VS2015 SSDT Report Wizard Style Selection Screen Not Showing

I am stumped on this one. I am not sure if others are having the same issue.
In past versions, when I use the report wizard, one of the screens lets me choose the style (Slate, Forest...)
With my new setup the screen never appears and on the summary screen it says 'Style:Modern'
I tracked down the StyleTemplate.Xml, made a copy and changed 'Modern' to 'ModernTest'. Both in the Styles folder and the en folder. I have searched my c drive and these are the only two places this file exists.
EDIT: I had to change the label to 'ModernTest' not the name. Now 'ModernTest' is showing up in the summary. I still however do not get the chance to change styles.
I added a new style to see if the page only shows up if more than one is present but maybe since that one was from an older version it still only thinks there is one valid style so skips the selection page... I will try to replicate modern...
I am using VS2015 Version 14.0.25123.00 Update 2, SSDT Version 14.0.1601.5
Anyone else have the same issue?
EDIT: I copied an xml file from a previous version and now slate appears as the style. I guess the only problem is that the screen to select the style no longer shows up.

Controls moving in vs2008 design mode on build

I have a C#.NET winforms project, and some controls are moving in design view whenever I build the project. Its only some of the controls (a panel with a label and datagridview in it, a button, a link button and a label) are all moving up on each build.
Has anyone seen this before or know how to fix it?
I think it is because of the AutoScaleDimensions. My guess is that your form was originally created on another machine.
Per MSDN.
"The AutoScaleDimensions property represents the DPI or font setting
of the screen that the control was scaled to or designed for.
Specifically, at design time this property will be set by the Windows
Forms designer to the value your monitor is currently using. Then,
when the form loads at run time, if the CurrentAutoScaleDimensions
property is different from the AutoScaleDimensions, the
PerformAutoScale method will be called to perform scaling of the
control and all of its children. Afterwards, AutoScaleDimensions will
be updated to reflect the new scaling size."
My guess is that for odd some reason when you build you project property (maybe some others) gets adjusted, but not on design time.
I think about few possible reasons:
You work on multiple monitors and/or there is some odd stuff with your adapter.
There is some problem with auto-generated designer file. Maybe it
edited manually somehow.
To fix I propose to do something I would do:
Recreate form from scratch if possible, by copy-pasting bits
one-by-one.
If not take some merging tool and insert fresh form
properties.
Also here is another interesting question on AutoScaleDimentions.

VS2010 Winforms Usercontrol changes not showing in parent form

I've created a series of usercontrols. Dragged one of the controls to the main form. It shows OK. Went back and made a change to the design of the user control. Rebuilt project. Cleaned project. manually removed all project binaries including the obj folder. Change still doesn't show on the usercontrol hosted on the main form. Dragging a new instance of the control from the tool box only shows the old version of the control.
Completely removed the controls from the toolbox and adding them again fixed the problem, but surely I don't have to do this everytime I make a change? All user controls are in the same assembly as the main form. Tool>Options>Windows Forms Designer>Auto toolbox Populate is set to true. Any ideas most appreciated. Thx
Do not add the control to the toolbox yourself. This puts a copy of the assembly in a private directory. Yes, this copy does not get updated automatically, you get the old control.
Rely on the "Auto toolbox populate" setting. It automatically adds any controls you have in your loaded project(s) to the toolbox. The added controls are at the top of the toolbox.
I agree with answer 1 that that is what is supposed to happen, and often does. But it doesn't always work and will work partially sometimes.
For example my current Solution.
Project 1 namespace ToolsTester - This is just a temporary form to test the view tools in the 2nd project.
Project 2 namespace UltimateFileFinder - This has three views.
The first 2 views (user controls) UltFilesView and UltSlideShow appeared as usual on the toolbar so I could drag them onto ToolsTester to try them out.
Then I added another user control UltPanel, this will not go onto the toolbox. Though it compiles without errors.
I have come across this problem a few times, sometimes removing and reasserting the reference fixes it. Other times I would have to remove the test project and create a new one.
I tested Visual Studio (full version) before release and this was one of the areas I reported back, so the problem was known pre-release.
This project I am on now I know that I will need to remove the test project and create a new one, in this case the tester is only a few simple caller and event responses, that is not always the case, there are times when the tester project can be quite complex because it is mimicing the target that the tools will be part of.

How can I programmatically trigger "Reset Column Layout" event on a winforms datagrid?

When releasing the latest iteration of our winforms application there is often confusion when users cannot see changes developers have made to a particular datagrid. Perhaps we've added, resized or re-ordered columns on purpose and we'd like users to benefit from the change. Because their local settings cache the grid layouts they must explicitly right-click and select "Reset Column Layout" to clear that cache and see the latest changes.
What I really need is a way of programmatically trigger "Reset Column Layout" command on grids that have changed in the latest iteration. It should probably only happen once, the first time they run the new build.
You could somehow have your installer remove the grid layout piece of the local settings. That way you'd make sure the layout would be reset and that it would only happen once.

Resources