Search found 74 matches
- Wed Sep 25, 2013 6:59 am
- Forum: Problems
- Topic: Designer Hotkeys / Shortcuts
- Replies: 2
- Views: 92489
Re: Designer Hotkeys / Shortcuts
Hello Mitica, I will answer your question with regards to Visual Studio 2012, as this code keeps changing with different versions. Most designer commands can be assigned using the Tools/Options menu, and going to the keyboard area. However certain shortcuts are hard coded. The shortcut keys are expl...
- Wed Jul 17, 2013 3:12 pm
- Forum: General
- Topic: VG.net 7.4 Released
- Replies: 3
- Views: 91180
Re: VG.net 7.4 Released
A customer identified a problem preventing the start menu link to VG.net 7 help from launching on a 64 bit system. If you have this problem, please contact us via the support page of the web-site, or on this forum, and we will email you a fix.
- Wed Jul 10, 2013 10:39 am
- Forum: General
- Topic: VG.net 7.4 Released
- Replies: 3
- Views: 91180
Re: VG.net 7.4 Released
VG.net 7.4b is released. This is a free upgrade for VG.net 7.4 users. The main change: Prodige.Drawing.dll now targets .net 4.0, allowing you to deploy on windows XP machines, which do not support .net 4.5. There are some minor documentation improvements as well.
- Tue May 07, 2013 7:59 am
- Forum: General
- Topic: VG.net 7.4 Released
- Replies: 3
- Views: 91180
Re: VG.net 7.4 Released
When you update your projects to use Visual Studio 2012, please check the .net framework target, and the Prodige.Drawing assembly version number. In Visual Studio 2012 you will need to use Prodige.Drawing.dll version 7.x, in order to have designer support. Update: In VG.net 7.4a Prodige.Drawing.dll ...
- Mon Jan 07, 2013 9:35 am
- Forum: General
- Topic: Visual Studio 2012 support
- Replies: 8
- Views: 144115
Re: Visual Studio 2012 support
Happy new year to you as well! We did the official announcement today (7th). Unlike the previous iteration (2008 to 2010), Visual Studio 2012 is an improvement over Visual Studio 2010. It is faster, may use less memory, and the documentation system is improved.
- Mon Jan 07, 2013 9:08 am
- Forum: General
- Topic: VG.net 7.4 Released
- Replies: 3
- Views: 91180
VG.net 7.4 Released
http://www.vgdotnet.com/blog/gauge_components_vs2012.png We released VG.net versions 7.4, 6.4, and 5.4. Changes include: Support for Visual Studio 2012, the SHOUTING MENU edition. Redesigned Picture Designer dialog windows: we reduced their size and made them more usable with all environment font s...
- Sat Dec 29, 2012 12:23 pm
- Forum: General
- Topic: Visual Studio 2012 support
- Replies: 8
- Views: 144115
Re: Visual Studio 2012 support
Hi Hugh,
It took longer than we thought. It is done. The official announcement will be on the 1st or 2nd. We uploaded the binaries today.
Regards,
It took longer than we thought. It is done. The official announcement will be on the 1st or 2nd. We uploaded the binaries today.
Regards,
- Thu Dec 13, 2012 9:51 am
- Forum: General
- Topic: Newbie question on picture instance names
- Replies: 5
- Views: 111390
Re: Newbie question on picture instance names
Hi Larry, When you add things in the designer, they are forced to have unique names. This is a requirement. If those names are serialized, the names are unique, within that Picture. I think you are seeing the name that is serialized by default for a top-level Picture, not a sub Picture. If your sub ...
- Wed Dec 12, 2012 5:31 pm
- Forum: General
- Topic: Newbie question on picture instance names
- Replies: 5
- Views: 111390
Re: Newbie question on picture instance names
Hi Larry, OK thinking about this I have a theory. You are catching the event at the level of the component. It is a top-level Picture. The top-level Picture has a name, however it will always be the same, as it is not a sub-Picture. When you add it to a Canvas dynamically it's name does not change. ...
- Wed Dec 12, 2012 5:16 pm
- Forum: General
- Topic: Newbie question on picture instance names
- Replies: 5
- Views: 111390
Re: Newbie question on picture instance names
Hello Larry, Please check the *.Designer.cs file to see if the Name property values were correctly serialized. If SerializeNames is set to true, you should see the code setting the Name property values. If not set, the Name of an Element is the empty string. Your code is exactly correct, except if y...