We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.

RecordNavigationBar: changing the asterisk

Thread ID:

Created:

Updated:

Platform:

Replies:

9496 Dec 21,2003 10:36 AM Dec 22,2003 01:03 PM Windows Forms 3
loading
Tags: GridControl
Colin Lamarre
Asked On December 21, 2003 10:36 AM

Hi, I want to change the asterisk in the RecordNavigationBar to something like "New". Don''t think the users here will know what an asterisk means. I''m using the RecordNavigationBar to navigate the db with a bunch of textboxes. Thank you

Administrator [Syncfusion]
Replied On December 22, 2003 02:04 AM

This AddNew icon is similar the one in Microsoft Access. That asterisk is actually a bitmap which is a private static member, ArrowPaint.starBmp, that is in the sealed class ArrowPaint. I don't see a simple way just to swap it out. If you have the source code, you could easily modify that to display a different bitmap, but then you would have to have build and a use your own version of Shared.

Colin Lamarre
Replied On December 22, 2003 04:05 AM

Hi Clay, I do have the source, but i can''t find an easy step by step guide to modifying and distributing a modified version. I know how to use the assembly manager, but even if i choose "force rebuild" it doesn''t take into account my mods. also there''s dups in workbook dir, what is workbook, do i modify those or not? i read something about signing the dlls, how do you do that? I am kinda new to dot net, started at the same time as syncfusion... forgive my newbie status! Thanks!

Administrator [Syncfusion]
Replied On December 22, 2003 01:03 PM

If you want to compile your own assemblies from our Syncfusion libraries and use them in the GAC, then you will have to use the strong name utility, sn.exe, to provide an appropriate snk file to sign your custom libraries. If you open up the Assembly.cs file from the Syncfusion.Shared project files, you will see some notes on signing your assemblies. So if you are making changes to the Shared source, then you will have to compile the modified library. And you will have to assign it a new strong name key using the sn.exe utility found in the \Program Files\Microsoft Visual Studio .NET\FrameworkSDK\Bin folder. 1) So, first create a snk file for your build by running sn.exe from a cmd prompt similar to: sn -k myCompany.snk (You can look up sn.exe in the online MS help for more information on this utility.) Then copy this snk file to the same folder (..\Syncfusion\Essential Suite\Shared ) that holds the sf.publicsnk file that the shared normally uses. 2) Then load the C:\Program Files\Syncfusion\Essential Suite\Shared\Src\Syncfusion.Shared.sln into VisStu. Open up the AssemblyInfo.cs file and look for the reference to sf.publicsnk in the code and replace it with your snk file ( myCompany.snk ). Also, change the Delayed signing attribute to false. Now rebuild the library. This should build a new Syncfusion.Shared.DLL in the Bin folder that uses your cahnged code and is signed with its own key so you can deploy it.

CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.

;