//
you're reading...
BetterMenu

Getting closer

I have one feature left to implement and I’ll be ready to release BetterMenu. Currently the width of the Rich Menu text will actually vary depending on the resolution the form was coded at and the resolution the user is running at. Because I have to rely on Code Serialization to store the resolution the form was created at the property storing the value is public. I want to stop the end-user from changing the value since the property is smart enough to pull the right value.

This is the part I can’t figure out…yet. With a nice weekend up ahead I think I’ll take advantage of it to finish the component off and get it posted here…then I’ll start back on the SyntaxHighlighter again πŸ™‚

Advertisements

About James

I am a Senior Developer/Consultant for InfoPlanIT, LLC. I previously spent over 7 years as a Product Manager for what eventually became ComponentOne, a division of GrapeCity. While there, I helped to create ActiveReports 7, GrapeCity ActiveAnalysis, and Data Dynamics Reports.

Discussion

One thought on “Getting closer

  1. Wan’t wait till you release it! I so want to have nice “BetterMenus” in my app πŸ˜‰

    Posted by Litchi | March 3, 2006, 9:59 am

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Archive

%d bloggers like this: