Itoo Software Forum

Author Topic: Request - Preserve Parameters if they are valid when loading profile  (Read 1471 times)

Rokas

  • iToo Software
  • Hero Member
  • *****
  • Posts: 2282
    • iToo
Re: Request - Preserve Parameters if they are valid when loading profile
« Reply #15 on: July 27, 2016, 09:15:50 AM »
Well tracking for modifications is not sustainable approach, in my opinion. I will write my detailed opinion and describe what I want and can`t do (if any) with the beta.
Rokas
iToo Software

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3600
    • iToo Software
Re: Request - Preserve Parameters if they are valid when loading profile
« Reply #16 on: July 27, 2016, 10:25:24 AM »
I appreciate your suggestions. We cannot introduce many changes in an update, but we can study other options for next major versions.

I think that local/global approach is fine for your custom sytles, but it may be a pain for library styles. We would get different opinions about if a parameter must be local or global (unless we decide Salomonically to define all of them as global).
For sure it's an interesting issue to discuss. :)

By the way, RC 2.7.1 beta is already available. If you want to check what parameters are modified, these are stored in "$.pamodifed" (array of booleans, one for parameter).
Carlos Quintero
iToo Software

Alex.S

  • Full Member
  • ***
  • Posts: 108
Re: Request - Preserve Parameters if they are valid when loading profile
« Reply #17 on: July 27, 2016, 12:05:59 PM »
IMO if a parameter is global then it should be a constant in the profile, not a parameter.

Thanks for the update, will check it out.

Rokas

  • iToo Software
  • Hero Member
  • *****
  • Posts: 2282
    • iToo
Re: Request - Preserve Parameters if they are valid when loading profile
« Reply #18 on: July 27, 2016, 12:58:54 PM »
We would get different opinions about if a parameter must be local or global (unless we decide Salomonically to define all of them as global).
For sure it's an interesting issue to discuss. :)
Of course global. For me RC is ruined as the productivity tool. Now it just a tool.

By the way, RC 2.7.1 beta is already available. If you want to check what parameters are modified, these are stored in "$.pamodifed" (array of booleans, one for parameter).

ok, that is helpfull I can stop whining and get back to work having maxscript ready: 
Code: [Select]
for obj in selection do obj.pamodified = #(false,false,false)I will find my way around using scripting, but if my experience and opinion maters anything, now it worse and less intuitive and clear what it is doing then old school way- overwriting everything.


IMO if a parameter is global then it should be a constant in the profile, not a parameter.
It should be global per scene, not  per style, don`t confuse the two. In some scenes You want wall height  to be 1 meter but other times 2 meters tall. And you want all walls to be the same defined Height.
So no, user should not hardcode that parameter, don't get me started.



My typical workflow:
I create one RC object,- most often put that to my custom library for future use. I make tons of variables to tweak the style.
Later, when I have to use the style (Hundreds of RC objects for hundreds of splines) I load it on one spline and tweak parameters to my liking.
Then I copy style to rest of the splines. And do further adjustments and again copying to all the splines to take effect . But now I cant!  (well I can with script mentioned above)
Rokas
iToo Software

Alex.S

  • Full Member
  • ***
  • Posts: 108
Re: Request - Preserve Parameters if they are valid when loading profile
« Reply #19 on: July 27, 2016, 01:09:05 PM »
Ah okay, sounds like you want a way to be able to set a single parameter to multiple objects - but not all, which would be nice indeed?

So many different ways people want to use the same thing :D

Alex.S

  • Full Member
  • ***
  • Posts: 108
Re: Request - Preserve Parameters if they are valid when loading profile
« Reply #20 on: July 27, 2016, 01:12:06 PM »
ok, that is helpfull I can stop whining and get back to work having maxscript ready: 
Code: [Select]
for obj in selection do obj.pamodified = #(false,false,false)I will find my way around using scripting, but if my experience and opinion maters anything, now it worse and less intuitive and clear what it is doing then old school way- overwriting everything.

You can disable it though? (edit. Or maybe not hmm...)
« Last Edit: July 27, 2016, 01:20:04 PM by Alex.S »

Rokas

  • iToo Software
  • Hero Member
  • *****
  • Posts: 2282
    • iToo
Re: Request - Preserve Parameters if they are valid when loading profile
« Reply #21 on: July 27, 2016, 01:20:15 PM »
thanx, life is beautiful again ;)
Rokas
iToo Software

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3600
    • iToo Software
Re: Request - Preserve Parameters if they are valid when loading profile
« Reply #22 on: July 27, 2016, 02:01:43 PM »
You can disable it though? (edit. Or maybe not hmm...)

That's it. Turning off both options, RailClone works as previous versions.
Retain parameters feature is optional, although enabled by default. My mention to $.pamodified was just only if you want to check current state of parameters.

« Last Edit: July 27, 2016, 02:03:34 PM by iToo »
Carlos Quintero
iToo Software

Alex.S

  • Full Member
  • ***
  • Posts: 108
Re: Request - Preserve Parameters if they are valid when loading profile
« Reply #23 on: July 27, 2016, 02:27:59 PM »
It is possible to edit params by scripts right? If so then most things are possible via that.

That said having an option to bulk set selected objects back to default params should placate most issues that people may have if they wish - perhaps on the RailClone lister, to use both settings?

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3600
    • iToo Software
Re: Request - Preserve Parameters if they are valid when loading profile
« Reply #24 on: July 27, 2016, 03:46:42 PM »
It is possible to edit params by scripts right? If so then most things are possible via that.

Yes, it's possible to modify parameters value from Maxscript (but not add or delete them). There is an array of values for each type ("paintval", "pafloatval", "paunitval" and "paboolval")

Quote
That said having an option to bulk set selected objects back to default params should placate most issues that people may have if they wish - perhaps on the RailClone lister, to use both settings?

Unfortunately default values are taken from the library, and these cannot be read without opening the browser.

The right way to reset all parameters should be to untick "General->Retain Parameters" and reapply the style from the library. If "General->Library update objects..." is off, changes are applied only to the selected object. If on, to all ojects sharing same style. This process also resets all "modified" parameter flags.
Carlos Quintero
iToo Software