Artisteer V. 3.0 final beta avail now Dec 23, 2010

A place for discussion about skinning and design. Before posting questions here you should review the documentation about creating skins.

This thread is closed to new posts. You must sign in to post in the forums.
1/4/2011 1:17:09 PM
Gravatar
Total Posts 6

Re: Artisteer V. 3.0 final beta avail now Dec 23, 2010

Thanks Joe, files sent.

1/5/2011 9:49:38 AM
Gravatar
Total Posts 18439

Re: Artisteer V. 3.0 final beta avail now Dec 23, 2010

Hi Mario,

Yesterday I made a fix in the Artisteer menu so that it now correctly highlights the currently active page. If you get the latest code and rebuild the solution I think you will find it works correctly.

The only other problem I noticed was the dynamic sub menu in your skin was using white text on a light colored background. This is probably caused by the javascript for the ASP.NET menu which sets some style on the menu that conflicts with the Artisteer CSS. I was able to fix it by adding this in your style-artisteer-overrides.css like this:

.art-menu a .t
{
  color: #232F13 !important;

}

the color is the same as defined in style.css but the !important makes it work around the style added by the menu javascript.

Hope it helps,

Joe

1/5/2011 3:09:41 PM
Gravatar
Total Posts 6

Re: Artisteer V. 3.0 final beta avail now Dec 23, 2010

Hi Joe, 

Thanks for the effort, but I can not pickup the changes. 

I did the following:

  • updated solution (VisualHG is showing this info: 731 (f7aa83012b33) default tip
    Merge changes from joedev branch)
  • cleaned and rebuild entire solution
  • published Web project to IIS
  • restored user.config and Data\Sites\1 folders

Active menu is behaving the same, could it be I'm updating from wrong branch in hg? Do I need to change anything in styles to make active menu work?

Thanks, 

Mario B. 

1/6/2011 6:51:32 AM
Gravatar
Total Posts 18439

Re: Artisteer V. 3.0 final beta avail now Dec 23, 2010

Hi Mario,

I think you are not getting the updates correctly, you should not be doing any merging nor using the joedev branch for anything, that is my developer sandbox, I merge my changes from there into the default branch and you should always use the default branch and never use my sandbox branch.

After you pull all change sets by using the green down arrow in Repository Explorer, then you need to close out of Repository explorer and right click the topmost folder and choose TortoiseHG > Update to apply the change sets to your working copy. In the update dialog make sure it points to the default branch do not update to my joedev branch.

I'm not sure the implications of the merging you did, you may need to get a clean clone of the repository if all else fails.

Hope it helps,

Joe

1/6/2011 2:23:07 PM
Gravatar
Total Posts 6

Re: Artisteer V. 3.0 final beta avail now Dec 23, 2010

Hey, 

I got it sorted, it was simply Hg doing stuff differently than I'm used to (svn). 

Thanks a lot for help, Joe. 

Mario

You must sign in to post in the forums. This thread is closed to new posts.