It seems a little strange with todays computing power to have Character Limitations when we are Naming Classes and setting up Working Files.
I also do no see any practical reason why there is a limit on the number of Subclasses any one Class can have.
It feels like legacy constraints from earlier Programing Conventions.
It would be nice to see this open up a bit.
Same should apply to removing limitations on Layer Naming Character Limitations. Though this does not seen as much of a bottle neck to work flow practices.
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
NHJ
It seems a little strange with todays computing power to have Character Limitations when we are Naming Classes and setting up Working Files.
I also do no see any practical reason why there is a limit on the number of Subclasses any one Class can have.
It feels like legacy constraints from earlier Programing Conventions.
It would be nice to see this open up a bit.
Same should apply to removing limitations on Layer Naming Character Limitations. Though this does not seen as much of a bottle neck to work flow practices.
That's just my 2 cents on that.
Edited by Our SpacesLink to comment
1 answer to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.