Please fix offset type issue, it's been 5 years!

[peter.phillipps]

I think the title says it all, stop bringing out pointless year on year updates with no real improvements while not fixing the bloody obvious things that show you don't listen to people actually using the product!

[jsanders]

It took about 4 years for Autodesk to be able to implement toggling from orthogonal to perspective view. You have to be patient mate...

[barthbradley]

Obviously you are frustrated. You do realize that you are preaching to the choir?  This is a USERS forum.   We all have developed workarounds over that years to mitigate for different limitations of the software. Perhaps, if you explain your issue, we can provide you with an acceptable workaround. Maybe one that is even better than what you want. 

Just  saying....

Edited by
Discussion_Admin

[Anonymous]

---

@jsanders wrote:

It took about 4 years for Autodesk to be able to implement toggling from orthogonal to perspective view. You have to be patient mate...

---

It was actually implemented a few releases ago....just sayin...

[Alfredo_Medina]

By the way, what is "offset type issue" that this thread is talking about?

[Anonymous]

I thought it might be when the Arial font jumps when rotated in tags..which isn't a Revit issue, it is the font.

<shrug>

[ToanDN]

I am trying to figure out what wasn't a problem five years ago but have been causing troubles since then. Emoji maybe?

[Anonymous]

The only other thing I could think of is that Offset in a family is always an instance and not a Type parameter?  

Which that would drive me crazy if it was a Type parameter.

[loboarch]

I thought maybe the issue was bulleted lists being a pain in the old text editor????

Hard to fix something when you are not even clear what the issue is.

[peter.phillipps]

when you type into the offset box, the cursor jumps almost instantly to the beginning so, for example when typing 35 it will be 53.

[peter.phillipps]

When you type into the offset box the cursor jumps almost instantly to the front, for example 35 wil come out 53, it is infuriating along with all the other annoying issues. 

Recently I have being dealing with Enscape, you email them and they reply with a timeline of the proposed improvements/fixes,  they have a public board where suggestions for updates can be posted and tracked, they release updates with these major updates every 3 months with minors between. 

[RobDraw]

---

@peter.phillipps wrote:

When you type into the offset box the cursor jumps almost instantly to the front, for example 35 wil come out 53, it is infuriating along with all the other annoying issues. 

---

Sorry, what is an offset box?

We really need more information to understand the issue.

[Alfredo_Medina · Accepted solution]

ah, ok, @peter.phillipps  thanks for the explanation.

I remember seeing that problem years ago, probably when I was using Revit 2014. I don´t remember seeing it in the recent versions. Most likely the problem was fixed between one version and the next. Which version of Revit do you use?

[peter.phillipps]

2018.3 hence my current annoyance at the copying model groups issue, there isn't a fix, I'm not looking for one I just want Autodesk to do better. 

[barthbradley]

What are you @Alfredo_Medina; Carnac the Magnificent or something?!  I still haven't got a clue what we're talking about on this thread.  Apparently you do.   Care to tell us what's in that envelope?

 

[RobDraw]

PEBCAK strikes again!

[Alfredo_Medina]

The problem is described in post # 11 above. 

I do remember seeing that problem. It was years ago, though.

[RobDraw]

This is what I see for #12:

---

@RobDraw wrote:

---

@peter.phillipps wrote:

When you type into the offset box the cursor jumps almost instantly to the front, for example 35 wil come out 53, it is infuriating along with all the other annoying issues. 

---

Sorry, what is an offset box?

We really need more information to understand the issue.

---

I still don't know what the OP's offset box is.

[Alfredo_Medina]

I added an image to my previous post.

[barthbradley]

---

@RobDraw wrote:

PEBCAK strikes again!

---

Funny, Rob. I had to Google that one. In other words: a loose nut behind the keyboard.  

@Alfredo_Medina: #12?  You pulling my leg, Carnac?  No matter. I'm moving on -- offsetting myself from this thread.