Mountains, menus and motors

I'm up in the mountains for the week as the kids have their winter half-term break (which in Switzerland is actually intended for kids to ski… very civilized :-). I'm going to take a few meetings and probably write a few blog posts, but otherwise I'm planning on hitting the slopes whenever I get the chance.

I did want to comment on how my research into right-click menus ended up, last week. I put together some code that made use of the technique shown in this previous post to create and load a partial CUIx file containing our OBJECT_ACAD_TABLE shortcut menu, but unfortunately it seems AutoCAD doesn't use such shortcut menus from "partial" files (i.e. those that aren't loaded as "main"). So the options are either to make our file the main one – loading acad.cuix etc. as partial files – or to do as we've done and add the options directly into acad.cuix. I'm far from being the CUI expert, though, so would love to have someone confirm this (Bob Bell – are you out there?).

Also, things are moving ahead with the project for the upcoming Geneva Motor Show. I've received my exhibitor's pass and will be heading over bright and early next Monday to help with the set-up of the Morgan stand (my part being largely software-related I can leave it until Monday – the stand will be built over the weekend and the show itself will kick-off with the press days on Tuesday and Wednesday). I did go to the show last year (and I'd been once or twice before that, some years ago), but this is the first time I'm participating in some way – it should be a very interesting experience. I'll explain more of what it's all about when the project is unveiled to the public, of course.

5 responses to “Mountains, menus and motors”

  1. Lucky is your middle name.

  2. Sadly it's actually "Roy" but I admit it's looking like a fun couple of weeks. 🙂

    Kean

  3. On the menu subject, think about the impacts of making a custom menu be the main.
    First, I have not seen things work right when things like the civil3d "civil" menu are not the main.
    Second, its no good having custom be the main menu as some places use such a menu in several profiles, even for several products. We have network c3d and acad, so it no good loading a custom menu with civil as partial, into an acad session. You get the civil menu because its daisy chained to the custom menu. That is the problem with the CUI system, its now daisy-chained, unlike the old system before 2006 where you had a main and unchained partials. Autodesk did not think that through and it comes up anytime you look at ootb profiles for acad and c3d. What should the main menu be? Autodesk is confused about that so let us know if you find someone who claims to understand the cui design intent. Bit of a rant but it remains broken IMO.

  4. Sounds as though modifying acad.cuix on the fly may actually be a better way to go in a number of scenarios (it's the best way I've seen to get custom shortcuts working, for instance).

    Kean

  5. plus.google.com/11667468544686 Avatar
    plus.google.com/11667468544686

    bahaha!

Leave a Reply to Kean Walmsley Cancel reply

Your email address will not be published. Required fields are marked *