I have an angular application (Angular5) running in visual studio 2017. I used ag grid (v7.0.2) earlier but recently upgraded to v18.0.1 after which certain features such as column filter and sorting stopped working. I am able to set properties in grid options for my grid and values such as enableColResize, showToolPanel are working as expected but not enableFilter/enableSorting. I tried to enables these properties in columnDef as well on each column but in vain.
Having said that, I am able to forcefully sort columns (after grid is initialized) but once that's done its not allowing me to change sort order.
The order of creating this grid is initializing it first (providing gridoptions) and then providing data.
Any suggestion is more than welcome!!
It was css overlapping issue. Though i have imported new ag-grid.css at a separate path but in final mark up, my app was referring old css as well which was causing filter/sort visibility issue.
Related
So I've inherited this Visual Basic project made with Winforms (originally .NET Framework 2.0 but I've set it to 4.8 as I need it. The problem exists in both versions. (Visual studio 2022, Windows 10)) but it has a problem.
Seen on the picture, left side is the design view where everything looks just fine. Right side however is when I run it. Some kind of padding on the right can be seen*.
If I look at the diff I can see the following (plaintext):
Now that Me.RibbonPanel1.Visible = True is what breaks it. I know that because if I remove it I get the following view:
Now the obvious solution would be to remove it, but it gets automatically inserted every time I enter the design view. You may also be able to notice that the last listview has a different size than in the first picture.
So besides never opening the design view, and when I do remember to remove it what can I do? There are lots of pages but none that behave like this.
* Yeah there's also the grey top bar, but I don't think I can do much about that (and I haven't heard the customers mention it)
It doesn't work if I try to add multiple pages to UNO SOLUTION. There are a lot of mistakes coming out. Only the UWP project is running. One of the mistakes.
LIST
First create a Page (Uno Platform UWP) then copy the body.
I also fixed the error in the same way.
To fix InitializeComponent error in Uno, you could refer to the following steps that are from the official document.
You could build your project once, close the solution and reopen it. It is also important to note that Uno uses a multi-project structure, for which each project has to be build individually for errors to disapear from the Error List window (notice the Project column values).
In order to clear the Error List window, build the whole solution completely once. Thereafter, build a specific project and prefer the use of the Output tool window (in the menu View -> Output), taking build messages by order of appearance.
Today, VS 2017 Community Edition recommended I take a small update, which I did.
Now any VB.NET solution that I open shows a blank form (as if adding a new form). However, in examining the files, all of the controls and the associated code are present in the files. It just appears that the VB.NET Form Designer is not happy with something in a file.
Is there anything I can do to kick the Form Designer to display the form correctly or is there anything I can examine to ascertain some specific error it might be throwing so that I can look in the right place for resolution.
I figured it out and thought the solution might be useful for others. For some reason, the new version was converting every VB Form control from this (for example) Me.labelFrequency.Location = New System.Drawing.Point(113, 197) to this Me.labelFrequency.Location = New System.Drawing.Point(-32768, 197)(Note the italicized invalid coordinate). It did this for EVERY control in the project. The negative coordinate was throwing off the Designer (obviously). I cleared the VSTS cache and restored a version of the xyzzy.Designer.VB file with the correct values and it stopped doing this. Left this here in case anyone else found this useful.
I am using VB.NET in Visual Studio Community 2017. I noticed that in some cases the list of available properties and methods for an object is incomplete.
One example can be seen here:
As depicted, I want to use the RowCount property of the dgv object, that is of type System.Windows.Forms.DataGridView. You can see, that right above it the property is there and working fine, I can just type it by hand. It just takes a second or two, before the background compiler (for lack of better term) acknowledges it as correct. The behavior messes up the typing flow, since often IntelliSense autocorrects what it perceives as typos.
Note: This is not exclusive to the shown property. I noticed it for other examples, and also in function calls and other random places, but I could not find a clear methodology of what is missing and what isn't.
Looking around I found e.g. this question, however it deals with a completely different problem.
Is this just a bug in Visual Studio (and if so, is it reported somewhere?), can someone confirm this, and does someone know of a fix?
Followed your steps and I got the same result like yours, I already reported this issue to the VS Product Team, please check this: VS 2017--VB: the intellisense for the DataGridView control not works like VS 2015, you can vote it or add a comment, then we need to waiting for the confirmation from the VS Product Team, thank you for your feedback.
Meanwhile, I tried it in C#>Windows Forms application and the intellisense works fine just like the VS 2015.
Albano Gheller posted an answer on the Visual Studio Community page.
To quote him and the required step for a fix:
I've fixed the problem in this way:
1. I've exported my settings from Tool - Import/Export settings
2. I've set the property HideAdvancedMembers = true inside
<ToolsOptionsSubCategory name="Basic" RegisteredName="Basic" PackageName="Text Management Package">
because C# has true and works
3. I've imported this modified settings.
So to summarize:
Find the part: <PropertyValue name="HideAdvancedMembers">false</PropertyValue> in the exported settings document's Basic ToolsOptionsSubCategory.
Change this to <PropertyValue name="HideAdvancedMembers">true</PropertyValue>, save, and then reimport the settings.
I don't know why hiding members leads to showing more members, but whatever ;-)
In supplement to Jens answer/to save anyone else some work:
Take the following XML, which is the minimum set of settings required to flip the problem attribute:
<UserSettings>
<ApplicationIdentity version="15.0"/>
<ToolsOptions>
<ToolsOptionsCategory RegisteredName="TextEditor" name="TextEditor">
<ToolsOptionsSubCategory PackageName="Text Management Package" RegisteredName="Basic" name="Basic">
<PropertyValue name="HideAdvancedMembers">true</PropertyValue>
</ToolsOptionsSubCategory>
</ToolsOptionsCategory>
</ToolsOptions>
</UserSettings>
Save it on the desktop in a file called a.vssettings
Go to Tools.. Import and Export Settings
Choose Import
Choose No, just import
Browse for the file you saved, do Next, Finish
I presume that there's a bug in VS where they got the boolean logic upside down for the intellisense, and advanced members are hidden when this attrib is false and shown when it's true
Is there only Horizontal Split as default and not Vertical Split? Again or my eyes are going bad? It was an issue in VS2008 and VS2010 when it was per-file basis so nothing has changed?
Yep there is currently no way of defaulting to a vertical split for the XAML designer in VS2012.
Like you mentioned the only way at this point is doing it per-file basis as these settings are saved together in your .suo file.
This applies to VS08 and VS10 or VS12...
If you do want to let microsoft know that you would like this to be a feature you can send them a request here
Here is the original thread about this issue.
Its funny though that their HTML designer does allow defaulting to vertical split..