Small width layout Medium width layout Maximum width layout Small text Medium text Large text
     Search
Downloads Downloads Directory Directory Forums Forums Forge Forge Blogs Blogs        Marketplace Marketplace Careers Program Careers
Community › Forums Register  |  

Maximum ASP
  Ads  
Iron Speed Designer is a software development tool for building database, reporting, and forms applications for .NET without hand-coding.
 


  Sponsors  

Meet Our Sponsors

Verndale
The Official Microsoft ASP.NET Website
Portal Webhosting - Hosting For Developers
Red-Gate Software
MaximumASP
SourceGear - Tools for Developers
 


DotNetNuke Forums
 
  Forum  DotNetNuke® Pro...  ClientAPI Compo...  Minimize/Maximized Image Problem
Previous Previous
 
Next Next
New Post 12/30/2005 12:29 PM
User is offline Jay Weaver
1 posts
10th Ranked


Minimize/Maximized Image Problem 

Hi -

I hope this is the right forum.  The Visibility module now calles the ClientAPI in version 3.2.2 to render the image or not.  The problem I'm having is when there is a postback (for example someone click the print icon) the is an empty image placeholder for the Minimize/Maximized when the container setting is set to "None".  I'm open to any suuggestions.

Thanks ahead of time.

 
 
New Post 1/12/2006 7:58 AM
User is offline Chris Krull
4 posts
10th Ranked


Re: Minimize/Maximized Image Problem 
Not sure about version 3.2.2, but with version 4.0.2 I have seen this error.  It appears that any module where the Visibilty is set to none and where the module can do a postback, the Minimize/Maximize icon is shown unsuccessfully.  Why show the icon if Visibility is set to None?  It appears that version 3.01 also shows the icon if Visibility is set to None, but shows it successfully.  I guess 3.2.2 was the initial move to calling the ClientAPI.
 
New Post 1/12/2006 8:13 AM
User is offline Jon Henning
1622 posts
www.codeendeavors.com
5th Ranked










Re: Minimize/Maximized Image Problem 
Actually this bug got introduced when the cleanup on v13wstat3 was done in the core.  The functionality assumed that the state would be maintained upon postback.  The issue is noted here with a workaround.  The real workaround will not need v13wstat3 and instead place logic in the page_load postback section of code.
 
 Page 1 of 1
Previous Previous
 
Next Next
  Forum  DotNetNuke® Pro...  ClientAPI Compo...  Minimize/Maximized Image Problem
 


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:

1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.
 


PartnerPoint | Community of Microsoft Partners
PartnerPoint is one of the largest and most active online communities of Microsoft Partners worlwide with over 8,000 members.
www.PartnerPoint.com 		Web Valley
Website design, Database development
www.webvalley.com 		UK DotNetNuke CMS installation, hosting & support
UK based installation, branding, customising, integration, hosting, training, support and maintenance services for DotNetNuke
www.deburca.co.uk

DotNetNuke Corporation   Terms Of Use  Privacy Statement
DotNetNuke®, DNN®, and the DotNetNuke logo are trademarks of DotNetNuke Corporation
Hosted by MaximumASP