Jump to content
AutoDesSys Forums

¢hris £und

Moderators
  • Content count

    1,109
  • Joined

  • Last visited

  • Days Won

    63

Reputation Activity

  1. Like
    ¢hris £und reacted to Justin Montoya in Why isn't formz more popular?   
    Just want to say Thanks for the sharing to everyone here.  I really love seeing all the passion for formZ and knowing I'm not alone in the world.  
    I don't often have to create detail drawings for my work.  We hand off the final concepts to a CAD dept expert,  where they work their magic to create real, usable shop drawings. 
    However, with that in mind, whenever I do want to create a detail type drawing for Estimating, I just do so in 3D using the Dimension and Callout tools.  Extra layers and extra files help to hide the unneeded model info (Now using Scenes since being told about them!), but if the main project and all the models get updated I would have to start it all again from scratch.  Does Layout fix that?  Does it create a reference to the main FMZ project and get automatically updated if the project gets updated?  I would use that if it did and was as easy to put together a document as just saving JPGs and compiling a PDF.
    That's something were missing.  The Best Practices Workflow.  Documentation and/or videos showing how to use these powerful tools.  I don't think it's obvious to many long time users, or even new users.  
    I believe Paul Helm made many of the videos we all used in the past and he was great at taking a sample project and explaining a few tools. I still reference the formZ animation videos!  Each video was short and direct about particular topics, without being too long or intimidating.  Layout needs this and probably all of formZ v9 for it's Tools and more since the interface has changed.  VRay for formZ needs it as well.
    I understand this is a big undertaking, and without volunteers, perhaps ADS is willing to hire someone with the expertise and passion for formZ who can do just what we need here?  I think that could be a huge first step and the videos on YouTube would also serve as valuable marketing material.  I'd particularly like to see some direct comparisons to competing products like SketchUp that could show how much more powerful and efficient formZ is out of the box, maybe a sample project like a simple building gets built in each program from start to finish?  formZ free should certainly be the hobby 3D printers/Makers dream software, powerful, free, upgradable.  Let's show some videos of it being used for that!  
     
    Keep up the suggestions folks!  Problems presented with possible solutions are always better heard.  Always.
  2. Like
    ¢hris £und reacted to Tech in what's new webinar   
    We had some technical issues with the recording plus we are cleaning up some rough edges (and prepping for this weeks webinar!). Please be patient, its coming but as these views tend to have a long shelf life so we want to get it right.
  3. Like
    ¢hris £und got a reaction from Alan Cooper in form•Z 8.6 Update Released   
    Alan,  
    Also, once you have manually reset all of your preferences for Z, make a copy of the pref folder so that you can manually do a swap in the future.
     
    ¢£
  4. Like
    ¢hris £und got a reaction from Des in Match 0.2 alpha Python Script WIP   
    Jaakko, John Alexander,
    Thank you very much! More scripts to come, And I do plan on ultimately converting them to plug-ins.  Scripting is easier though.
    John, That is pretty much the extent of my Hot Air Balloon Designs.  There are two others, but I do not have photos of them.  One of those, I merely augmented an existing balloon.  They are all Home builds, so they are classified as Experimental Aircraft.   I am not a licensed aeronautical engineer, so am not legally allowed to design them.  Home builds/experimental is the loophole. 
    All the other designs are what are classified as cold air or forced air inflatables.  Primarily for advertising purposes.  Always considered myself a low grade industrial designer.  Dan Manoim (sp)  is the goto Guy for fZ industrial design.   He pops in now and again (I think, DanM?)  I have done other work, but mostly as the last guy on the list, so, clients never knew of me.   Don't know if I am allowed to show any of that work.  Some of that was, Denver International airport. (Flight Information Displays), Concepts for Arm and Hammer, Evian, Prototype This TV show (Personal Air Bag Safety device) Sadly only lasted 1 season, Intact Labs (project for NASA), JRF Visuals only, Evian water bottle, Hunter Douglas, Corona and some others.
    Most of the things on that list never amounted to anything.   the FIDs got built, and the Prototype this got built.  My anonymous claim to fame.
    here is some of the CABallon work, however.  (I no longer do this work, company was purchased, and the new company moved all design and production to South America)
    Thanks for the interest!
    The Dragon was probably one of the funnest projects, as I got to do the electronics and write the code for it too.
    And, Yes FormZ was crucial in each of these projects.
     
     
    Me tweaking some of the Micro-controller code
    Video of the Dragon: http://www.neurascenic.com/Dragon2.m4v
     


  5. Like
    ¢hris £und reacted to santa in formZ models exchange site!   
    Chris,
    Yes it would be nice, but I am wondering if Anton will be prepared to undertake such a task on his own. Running, maintaining, and paying for a server 24/7, in addition to associated site hosting, is not for the faint of heart!
    It seems to me that it would be best if autodessys stepped up and offered some space on its servers and forums. How about it Z?
  6. Thanks
    ¢hris £und reacted to Andrew West in formZ models exchange site!   
    Anton
    Is there any chance that we could get this model site up and running again?  What would it take?  I have dozens of models that I would like to share.  I always felt that Form.z needed a site similar to the Sketchup Warehouse in order to expand their user base.  I would also like to share materials and texture maps that would help others.  I have hundreds that I could post.   
  7. Like
    ¢hris £und got a reaction from Bo Atkinson in Why isn't formz more popular?   
    I too have been using fZ for about 25 years.  Started at the 2.6 ish?  My introduction to it was through Electric Image animation system. As that was what I was doing at the time. EIAS, was hugely on the side of fZ as the best modeler.  At the time, I was using light wave on the amiga to model, but animated using EIAS on the Mac. In that job, I discovered that I preferred modeling to animating, so when I left (freely interpret that as being payed off with prejudice), I jumped to fZ.  
     Yes, v7 was buggy and I stuck with 6.x until 8.5. For my production work.   Up through 6.x it was pretty solid.  However 7 (aka Bonzai core). Was a rewrite that was needed. Bonzai was written as the platform to experiment on for a new interface and core of the program. Once it was at a good enough level, they made the transition for fZ. Something like that is a monumental undertaking, but ADS saw the writing on the wall, so they did it. for me, 7-8.4.x. Was lacking in some of the features I needed.  Up to fairly recently, I really needed the C- mesh back...   don’t need it any more though. And I made due with Modo to fill in and Z being the 80% left over that I needed.   Scripting has been the toughest part for me.  While FSL was technically available n 7-8.5. It kind of became the bastard child and not maintained.  I am not criticizing ADS for this, as long term, I think they made the right discussion to move to Python.  (A request of mine, but I am sure I wasn’t the only one). While FSL does have the advantage of it being easier to migrate your code to C/C++ than will be from python to C/C++.   For the professional programmer who wants to prototype in python, this won’t be a problem.   For the casual coder, python is a world easier than FSL as FSL was really C syntax. This user probably won’t care to bother converting it to C/C++ any way.  Which, In my view will be a profound advantage.      Back when the FSL API was introduced, there was no reason to expect python to take over as it did, so no reason for them to build it that way.   The change could not have been trivial. I suspect that the C/C++ API has changed as well.  We are to soon reap the benefits of those efforts.  It is my hope that ADS will change to Python 3.8.  But that will not stop me from jumping in.   The power of scripting is ours to wield. This will allow us to creat the niche scripts that maybe only we need and not the whole community. Therefore not burdening ADS with the effort for a little used tool. Those who need that tool however, can benefit from it immensely.   I have many questions regarding the new API, that I haven’t been able to figure from the examples they provided.  Those should be answered soon. 
     
    to ADS, thank you for your efforts, and thank you for tolerating my being a royal PIA regarding scripting during this period. 
    anybody up to learn scripting,  I guarantee it will be worth your time. Especially now that python is it.  As python has many uses outside of fZ.   
    example, I automated a task In my last job that took a minimum of 10 minutes to accomplish and reduced it to about 35 seconds. Well worth all the effort to learn.  
     
    Be open to learning it, and share, if you can. 
     
    apologies for the stream of consciousness.  I’ll leave you all alone for the time being. 
     
    €£
  8. Like
    ¢hris £und got a reaction from Des in Match 0.2 alpha Python Script WIP   
    Jaakko, John Alexander,
    Thank you very much! More scripts to come, And I do plan on ultimately converting them to plug-ins.  Scripting is easier though.
    John, That is pretty much the extent of my Hot Air Balloon Designs.  There are two others, but I do not have photos of them.  One of those, I merely augmented an existing balloon.  They are all Home builds, so they are classified as Experimental Aircraft.   I am not a licensed aeronautical engineer, so am not legally allowed to design them.  Home builds/experimental is the loophole. 
    All the other designs are what are classified as cold air or forced air inflatables.  Primarily for advertising purposes.  Always considered myself a low grade industrial designer.  Dan Manoim (sp)  is the goto Guy for fZ industrial design.   He pops in now and again (I think, DanM?)  I have done other work, but mostly as the last guy on the list, so, clients never knew of me.   Don't know if I am allowed to show any of that work.  Some of that was, Denver International airport. (Flight Information Displays), Concepts for Arm and Hammer, Evian, Prototype This TV show (Personal Air Bag Safety device) Sadly only lasted 1 season, Intact Labs (project for NASA), JRF Visuals only, Evian water bottle, Hunter Douglas, Corona and some others.
    Most of the things on that list never amounted to anything.   the FIDs got built, and the Prototype this got built.  My anonymous claim to fame.
    here is some of the CABallon work, however.  (I no longer do this work, company was purchased, and the new company moved all design and production to South America)
    Thanks for the interest!
    The Dragon was probably one of the funnest projects, as I got to do the electronics and write the code for it too.
    And, Yes FormZ was crucial in each of these projects.
     
     
    Me tweaking some of the Micro-controller code
    Video of the Dragon: http://www.neurascenic.com/Dragon2.m4v
     


  9. Like
    ¢hris £und reacted to Jaakko in Match 0.2 alpha Python Script WIP   
    Great work Chris! Thanks for sharing.
  10. Like
    ¢hris £und got a reaction from Tech in Match 0.2 alpha Python Script WIP   
    Hello all,
    My first attempt at a fZ/python script.  (this is an Alpha and has known issues.  ToDo List at the bottom of this message.)  File attached. 
    What is Match? 
    Match will scale objects to match the Boundary Length (not yet functional), Area, or Volume.  Not the bounding dimensions. Either Source/Master objects or a direct value in the UI can be used to determine the Target object sizes.  Scaling is also allowed. Such as 1.5 x  or .3333 of the Master.
    Match, is shape/form agnostic.  That is, it doesn't care what the Target, nor Master shapes are, it will work as long as they have the topology you are trying to Match.   i.e.  a open poly line does not have a volume, so the script will not work if attempted. (currently, if an error is raised, nothing happens, including no indication of the error)
    A surface objects area could be matched to the surface of a Solid, if you have a reason to do that, and visa versa.  Likewise a surface objects length can be matched to a open or closed line form and visa versa.
     
    Hope this is useful for someone besides myself.
     
    ---------------------------
    To use:  (if the .pyc file doesn't work on a PC, let me know, I will provide the source if need be)
    Manually Install the script in the scripts folder (as far as I can tell, this cannot be in a sub-folder)
    Abstract case:  Select the objects.   Currently, Last object created will act as the Master/Source.  All other objects selected will act as Targets. (This will be fixed in the future)    So, cut and paste the object you want to be the master, so that fZ regards it as the last object in the modeling buffer.  This will be fixed in the future.
    Here are three arbitrary objects all with differing Volumes.  The Pyramidal shape will be the Master, as it is the last object created.

     
    Master.                                                              Target                                                                 Target
     
    1. Select the objects you want to transform as well as the Master.
    2. Chose, Extension/Run Utility, Navigate to the Match.pyc script.
    the following dialog should appear.

    Select your options,
    In, this case, I am going to match the Volume Topology of the Pyramidal shape, with no scaling.
    Click the OK button, Now the objects all have the same Volumes.

    Note 1: the surface areas are all different, while the Volumes all "Match"

     
    TODO List.  (I will need the API Documentation to finish)
    • Change UI to make sense.    The order of the UI is a little awkward right now.
    • User configurable Units (currently only Imperial Units work and in Feet Only)  (really only matters when inputing size manually into the UI.  If matching to an existing volume, works as expected)
    • Use Pick Order (currently, the last object created is the Master that all other objects picked gets matched to)  (Allow User to have first picked or Last Picked to be the Master by UI Choice)
    • Minor issue with the Volume, does not always make a perfect match.  is sometimes off by a few thousands. (I do know how to fix it... just need to jump on it)
    • Undo doesn't work, Not sure if that is my problem or something
    • Clean up and Document Code
     
    The script was built from what I could glean from the examples provided by ADS.  Realistically, this is a simple project, however it does hint at the power of what can be done.
    The future is bright!
     
    Next, I will show some examples of Why you would want to use it.

    Match.pyc
  11. Like
    ¢hris £und got a reaction from Tech in Match 0.2 alpha Python Script WIP   
    Example Usage 1.
    Intake/Exhaust using Cross sections to generate final object.  
    Here is the final object.

    This object has the same cross section throughout, regardless of the cross section shape. Except the final rectangle, it is reduced 75% of the intake (cropped circle).
    The Following is how I built it using the Match Script.
    First I created the rough source shapes, with no regard to their areas, and placed them roughly where I wanted them.   There are 3 circles in the center, to help the loft tool maintain the desired cross section (can get a little wonky when changing shape types. it will bulge if only 2 circles are used.)

    Making sure the master shape is the last one created, I cut and paste one of the intake shapes (again, the cropped circle)
    Select all the objects I want to scale to the same area as the intake (all except the last of exhaust rectangles, I am saving that for another operation)
    Launch the script from the Extensions/Run Utility Menu
    Select Topology/surface. scale 1.0

    Click OK.
    Areas of the 6 objects now match the intake.
     
    I repeat the process again, but this time only select the intake cross (it is still the last object created) section and the final exhaust port cross section.
    Run the script again and change the following settings:  Topology/Surface.   and Scale to .75

    Click OK.

    Select the cross sections in order and apply the loft tool.

     
    more advanced examples.

     
  12. Like
    ¢hris £und got a reaction from Tech in Match 0.2 alpha Python Script WIP   
    Example 2, without directions, as hopefully, it is now clear what the script is for.
     
    Here is a real world example. of matching a volume to a pre-specified volume via the UI.
    Was given the requirement that the balloon have a specific Volume.  Enough to carry the weight of the basket, passengers, and the balloon itself.   But not so big, that it became cost prohibitive to build.   The actual volume was provided.   (I used the same math to figure this out, as the script did not exist 15 years ago, but planted the seed for the script)
     

     
    Other Balloons for the same client, only Sylvester got built, albeit pupils in the wrong spot, and he decided not to put the tongue on.

     
     
     
     
     
  13. Like
    ¢hris £und got a reaction from Tech in Match 0.2 alpha Python Script WIP   
    How I use Example 1:  this is still a WIP, but should suffice as a concrete example.


     
    Will stop pestering all of you now.
  14. Like
    ¢hris £und got a reaction from Tech in Match 0.2 alpha Python Script WIP   
    How I use Example 1:  this is still a WIP, but should suffice as a concrete example.


     
    Will stop pestering all of you now.
  15. Like
    ¢hris £und got a reaction from Tech in Match 0.2 alpha Python Script WIP   
    Example 2, without directions, as hopefully, it is now clear what the script is for.
     
    Here is a real world example. of matching a volume to a pre-specified volume via the UI.
    Was given the requirement that the balloon have a specific Volume.  Enough to carry the weight of the basket, passengers, and the balloon itself.   But not so big, that it became cost prohibitive to build.   The actual volume was provided.   (I used the same math to figure this out, as the script did not exist 15 years ago, but planted the seed for the script)
     

     
    Other Balloons for the same client, only Sylvester got built, albeit pupils in the wrong spot, and he decided not to put the tongue on.

     
     
     
     
     
  16. Like
    ¢hris £und got a reaction from Tech in Match 0.2 alpha Python Script WIP   
    Example Usage 1.
    Intake/Exhaust using Cross sections to generate final object.  
    Here is the final object.

    This object has the same cross section throughout, regardless of the cross section shape. Except the final rectangle, it is reduced 75% of the intake (cropped circle).
    The Following is how I built it using the Match Script.
    First I created the rough source shapes, with no regard to their areas, and placed them roughly where I wanted them.   There are 3 circles in the center, to help the loft tool maintain the desired cross section (can get a little wonky when changing shape types. it will bulge if only 2 circles are used.)

    Making sure the master shape is the last one created, I cut and paste one of the intake shapes (again, the cropped circle)
    Select all the objects I want to scale to the same area as the intake (all except the last of exhaust rectangles, I am saving that for another operation)
    Launch the script from the Extensions/Run Utility Menu
    Select Topology/surface. scale 1.0

    Click OK.
    Areas of the 6 objects now match the intake.
     
    I repeat the process again, but this time only select the intake cross (it is still the last object created) section and the final exhaust port cross section.
    Run the script again and change the following settings:  Topology/Surface.   and Scale to .75

    Click OK.

    Select the cross sections in order and apply the loft tool.

     
    more advanced examples.

     
  17. Like
    ¢hris £und got a reaction from Tech in Match 0.2 alpha Python Script WIP   
    Hello all,
    My first attempt at a fZ/python script.  (this is an Alpha and has known issues.  ToDo List at the bottom of this message.)  File attached. 
    What is Match? 
    Match will scale objects to match the Boundary Length (not yet functional), Area, or Volume.  Not the bounding dimensions. Either Source/Master objects or a direct value in the UI can be used to determine the Target object sizes.  Scaling is also allowed. Such as 1.5 x  or .3333 of the Master.
    Match, is shape/form agnostic.  That is, it doesn't care what the Target, nor Master shapes are, it will work as long as they have the topology you are trying to Match.   i.e.  a open poly line does not have a volume, so the script will not work if attempted. (currently, if an error is raised, nothing happens, including no indication of the error)
    A surface objects area could be matched to the surface of a Solid, if you have a reason to do that, and visa versa.  Likewise a surface objects length can be matched to a open or closed line form and visa versa.
     
    Hope this is useful for someone besides myself.
     
    ---------------------------
    To use:  (if the .pyc file doesn't work on a PC, let me know, I will provide the source if need be)
    Manually Install the script in the scripts folder (as far as I can tell, this cannot be in a sub-folder)
    Abstract case:  Select the objects.   Currently, Last object created will act as the Master/Source.  All other objects selected will act as Targets. (This will be fixed in the future)    So, cut and paste the object you want to be the master, so that fZ regards it as the last object in the modeling buffer.  This will be fixed in the future.
    Here are three arbitrary objects all with differing Volumes.  The Pyramidal shape will be the Master, as it is the last object created.

     
    Master.                                                              Target                                                                 Target
     
    1. Select the objects you want to transform as well as the Master.
    2. Chose, Extension/Run Utility, Navigate to the Match.pyc script.
    the following dialog should appear.

    Select your options,
    In, this case, I am going to match the Volume Topology of the Pyramidal shape, with no scaling.
    Click the OK button, Now the objects all have the same Volumes.

    Note 1: the surface areas are all different, while the Volumes all "Match"

     
    TODO List.  (I will need the API Documentation to finish)
    • Change UI to make sense.    The order of the UI is a little awkward right now.
    • User configurable Units (currently only Imperial Units work and in Feet Only)  (really only matters when inputing size manually into the UI.  If matching to an existing volume, works as expected)
    • Use Pick Order (currently, the last object created is the Master that all other objects picked gets matched to)  (Allow User to have first picked or Last Picked to be the Master by UI Choice)
    • Minor issue with the Volume, does not always make a perfect match.  is sometimes off by a few thousands. (I do know how to fix it... just need to jump on it)
    • Undo doesn't work, Not sure if that is my problem or something
    • Clean up and Document Code
     
    The script was built from what I could glean from the examples provided by ADS.  Realistically, this is a simple project, however it does hint at the power of what can be done.
    The future is bright!
     
    Next, I will show some examples of Why you would want to use it.

    Match.pyc
  18. Thanks
    ¢hris £und reacted to jwiede in Swift   
    For another example, check out RemObject's object Pascal (Oxygene), C# and Swift toolchains, for Windows, Linux, and macOS.  They've also done quite a bit of work into cross-platform & cross-language-toolchain integration with those languages.
  19. Thanks
    ¢hris £und got a reaction from andrew in Catalina (MacOS 10.15) compatibility   
    https://s3.us-east-2.amazonaws.com/formz9.autodessys.com/Install_formZ_Lab.dmg
     
  20. Thanks
    ¢hris £und reacted to Tech in form•Z v9.0.1 now available   
    form•Z v9.0.1 (#A107) 
    We have posted v9.0.1 today to address some reported issues with formZ v9. This version can be now installed using the link you received with your v9 codes. Here is a list of some of the more important improvements:

    • When the favorites menu is invoked (Space bar by default), pressing the space bar again will open and position the tool options palette on the screen at the location of the favorites tools. This makes for an easy way to access the Tool Options without needing to navigate to the location of the palette. The palette is returned to its original state when the mouse moves out of the newly positioned tool options palette or the favorites menu shortcut is selected again.
    • Pop-up Tool Options is a new key shortcut available in the Palettes group of the Key shortcuts manager. This invokes the tool options at the mouse location as with the favorites menu without needing to go through the favorites menu first. There is no default key combination assigned for this option.
    • The color popup in the Attributes tab of the Inspector now works properly when clicking on the arrow indicator.
    • Export PSD no longer generates empty files under certain situations.
    • The palette dock is now maintained in the Cone Of Vision environment.
    • Shaded work and shaded full now show the proper color when Copy and paste of objects which have materials with matching names.
    • Certain geometry no longer causes a crash when using object snaps and the mouse rolls over the object.
    • Create Reference File no longer includes references to other attached reference files in the newly created reference file.
    • Create Reference File now warns when replacing a reference file that is already being referenced by the project.
    • Create Reference File now handles single object reference files properly.
    • Docking and undocking certain palettes now works properly.
    • Editing Components in the project window has been improved.
    • The parameters tab of the inspector now works properly with components.
    • Components placed with the “Place on Active Layer” option now explode properly.
    • The “Getting Started” tutorials are now accessible from the startup screen again.
    • Holding Command/Ctrl and dragging docked palette will allow precision
placement/force placement
        
    OS X specific 
    • Installer now works better on OS X 10.15.3
    • Animations played in the form•Z window now display properly.
    • Closing the Inspector palette, no longer leads to crashes. 
    • Changing the direction of the Arc 3 again works with tapping command key.
    Windows specific 
    • Hide palettes no longer leads to extra margins shown around the palettes when un-hiding. 
        
    Draft Layout
    • Title blocks now work as expected.
    • The place image tool now works as expected.
    • Components update properly when a layout file is opened.
    • Paste from Model/Paste from Draft have been improved.
    • Compounds from v6 files are now converted properly.
    Additional stability and performance improvements.
  21. Like
    ¢hris £und got a reaction from Des in MIMI updated :: Sort of   
    As it currently Stands, no.  The new API is based on python, not FSL, which is what MIMI is written in.  ADS is working on real easing the new API and documentation. Once I have the documentation, I will get to work on it.  While I have been able to figure some things out without the documentation, not totally. As, everything figured so far is from their examples.
    Am also wondering at this point, to what the changes are in the C/C++ API are.  from what I can see, 9 doesn’t load 8.5.6 plugins either. Which is interesting. Could be something simple, and not significant.  Can’t help but wonder though. 
     
    thanks for the props on MIMI, it is appreciated.  I do intend on making it more useful as well.   Such as, setting a base material  so that all imported maps share its settings but the map itself.  Other shaders, not just renderzone.  Open to suggestions as well. 
     
    cheers!
    €£
  22. Thanks
    ¢hris £und got a reaction from andrew in Catalina (MacOS 10.15) compatibility   
    https://s3.us-east-2.amazonaws.com/formz9.autodessys.com/Install_formZ_Lab.dmg
     
  23. Like
    ¢hris £und reacted to andrew in Why isn't formz more popular?   
    Participation is the key, imho. "Tech" was very candid in this thread setting the record straight and sharing some insight. Its never easy to run a small company in today's world and get it all right all the time. I sense a renewed commitment with the release of v9 and the discussion of improving vRay to next. Do we all crave info and insight so we can make decisions about how we use these tools in many different workflows? Yes. We deserve to know as much as ADS can share about the platform.
     If we share out work, contribute on the forum, participate in the beta tests and submit bug and questions to ADS with this community will grow and keep thriving. Bigger is not always better, but quality and playing well with others always brings excellence and richness to life. I'm glad to have a robust community of dedicated users to share with and I'm thankful that formZ is still the best creative environment for scaled, detailed design and modeling work.
    Thanks for reading my thoughts. I'm really grateful for all of you.
     
  24. Like
    ¢hris £und reacted to kim in Hardware - Input Devices   
    Hi Chris,
    This is a game changer!  Maybe I won't need a new mouse :-).
    Many thanks.
  25. Like
    ¢hris £und reacted to kim in Too Options Palette   
    In FZ 8.5 I had the Tool Options Palette separated from the Palettes window and sitting in the top right hand corner of my screen.  Regardless as to what I was doing with the other palettes I could always keep my eye on the options palette to check what was going on.
    With the new FZ window being a contained cell, the only way I can separate the Tool Options Palette is to place it away from the right side of the screen.  As it is open all the time, I then lose valuable real estate for modeling.  
    I would be curious if anyone has figured out a work around to the new palette structure?  And then a question for ADS. Would it be possible to place the Tool Option Palette in the top right hand corner and lock it so that the other palettes would scroll under it.  Similar to how the Header Row and Column system work in spreadsheets?  Currently the options on a palette window are "Detach, Move to Left, Move to Right."  How about a "Lock Palette" Option?
×