General table deleting exiting text when inserting additional text

[cjackson9613]

Has anyone else and an issue with existing text within a general table deleting while inserting additional text?

We have a general table that is within our template that has text, we insert the addition text needed. Each time I start typing, all the text in front of the cursor is deleted. It acts like I have the text selected or the insert is on (which they are not) and removes it as I type. This problem only started when the most recent update was done.

[cjackson9613]

This issue is occurring with all our drawings. Not just new ones. Existing drawings that are in our vault are having this issue.

[Curtis_Waguespack]

Hi cjackson9613,

What version of Inventor are you using?

What OS (Win 7, Win 10, ,?)

I hope this helps.
Best of luck to you in all of your Inventor pursuits,
Curtis
http://inventortrenches.blogspot.com

[cjackson9613]

2018

Windows 7

[ChrisMitchell01 · Accepted solution]

Hello,

Yes, unfortunately this issue was discovered post 2018.1 release. A fix is actively being worked on. As of now the only workarounds are to copy all the text then edit it say in word etc & paste it back appropriately, or uninstall 2018.1 😞

Sorry to be the bearer of bad news.

Chris

[bob_holland]

@cjackson9613

I wanted to let you know that I have created a tracking page for this issue:

http://knowledge.autodesk.com/article/Inventor-2018-s-general-table-deleting-exiting-text-when-inser...

The above link should be live by tomorrow morning.

Have a great rest of your week.

[Anonymous]

Experiencing same issue here

Existing text obliterated when editing (adding to) tables, change blocks etc.

Breaking text editing programmatically !?@#*

IV 2018 / Win 7

[mcgyvr]

---

@Anonymous wrote:

Experiencing same issue here

Existing text obliterated when editing (adding to) tables, change blocks etc.

Breaking text editing programmatically !?@#*

IV 2018 / Win 7

---

Anyone on 2018.1 is experiencing the same issue..

They let a bug out in 2018.1 and that bug is there for everyone to see..

[ChrisMitchell01]

We hope to release 2018.1.1 to address this within about a week or so. It's just being packaged today & will be tested next week.

Sorry for the inconvenience,

Chris

[mcgyvr]

---

@ChrisMitchell01 wrote:

We hope to release 2018.1.1 to address this within about a week or so. It's just being packaged today & will be tested next week.

Sorry for the inconvenience,

Chris

---

Hopefully you squashed the chamfer bug in that one too.. 

[johnsonshiue]

Hi Brian,

Yes, the Chamfer width input issue is also fixed on an internal build targeting the .1.1 update. I am very sorry for these regressions. In a hindsight, we took a little bit more risk to accept more fixes than we would in the past. Unfortunately, these slipped through the crack. We have made process change to ensure things like this will not repeat.

Many thanks!

[Anonymous]

Sorry, question. For 2018.1.1 The environment variable UseLibXL is no longer required, and should be removed from your system as it can prevent Excel from being used for table write operations? Performance (iPart, iAssembly) is very different for my system with UseLibXL=1 and without UseLibXL. Without UseLibXL better. PDSU 2018.1.1/Win 10 64/2x Xeon E5630/24Gb/Quadro P1000/2x SSD WBR Andrey

[mcgyvr]

---

@Anonymous wrote:
Sorry, question. For 2018.1.1 The environment variable UseLibXL is no longer required, and should be removed from your system as it can prevent Excel from being used for table write operations? Performance (iPart, iAssembly) is very different for my system with UseLibXL=1 and without UseLibXL. Without UseLibXL better. PDSU 2018.1.1/Win 10 64/2x Xeon E5630/24Gb/Quadro P1000/2x SSD WBR Andrey

---

@Anonymous Are you saying now that you have 2018.1.1 loaded and you have removed that environmental variable as its supposedly not needed anymore that excel performance is better?

If it is then.. Good.. Autodesk did their job..

If not then they failed and they need to know that performance is worse

[ChrisMitchell01]

Inventor uses Excel in many different workflows. The predominant complaint & the primary reason for setting that environment variable was to improve the performance of creating holes, (which by default was using Excel to read the xls file containing all of the various information).

Setting the variable told Inventor as a whole not to use Excel but to use the LibXL libraries instead which are more performant but not as functional as Excel. This works fine for read only based operations such as creating holes but not for write based operations such ass editing iparts/iassemblies using Excel.

The work done in 2018.1.1 was to always use libXL for the hole based functionality regardless of whether the variable was set or not. So if the the variable was being set to improve the performance of the hole dialog then it is no longer required.

If however, you were setting it to improve the performance of iparts/iassemblies then it may still be needed. Note that by setting it you may not be able to properly edit iparts/iassembly tables using excel anymore. Other functions such as animating pos reps in Studio may not be fully functional with the variable set.

The work to completely remove the dependency on Excel across all of Inventor is a large project that is being approached in the order of command usage in order to maximize ROI.

Hope this clarifies,

Chris

[Anonymous]

About UseLibXL in 2018.1 update:

... Attention: The environment variable UseLibXL is no longer required, and should be removed from your system as it can prevent Excel from being used for table write operations. ...

See http://help.autodesk.com/view/INVNTOR/2018/ENU/?guid=GUID-35383566-95AE-4F7A-AEA7-C27CB0ACCE18

I install update 2018.1 and after the test without UseLibXL I return to work with UseLibXL=1 due to performance problem.

I install update 2018.1.1 and after the test without UseLibXL I return to work with UseLibXL=1 due to performance problem.

iPart & iAssembly > 90% of my work.

PDSU 2018, Win 10 64, MSOffice 2016 (all update) / Intel S5520SC, 2x Xeon E5630, 24Gb, 2x SSD, Quadro P1000, 32" + 24", SpaceNavigator

WBR Andrey

[Anonymous]

Thanks, All OK.

iPart & iAssembly > 90% of my work.

[mcgyvr]

---

@ChrisMitchell01 wrote:

Inventor uses Excel in many different workflows. The predominant complaint & the primary reason for setting that environment variable was to improve the performance of creating holes, (which by default was using Excel to read the xls file containing all of the various information).

Setting the variable told Inventor as a whole not to use Excel but to use the LibXL libraries instead which are more performant but not as functional as Excel. This works fine for read only based operations such as creating holes but not for write based operations such ass editing iparts/iassemblies using Excel.

Hope this clarifies,

Chris

---

@ChrisMitchell01 So you can't do anything about the performance degradation with write operations?

Correct me if I'm wrong but the performance took a pretty big hit a couple releases ago and hasn't been improved upon from what I've been reading here on the forums from other users.. 

You also should update that note generically stating that the env variable can/should be removed to add some clarification as to what it can/can't do.. Thats making people (like I just did) assume that you actually fixed the issues and you did not..  Its another half finished attempt.. 

[ChrisMitchell01]

I had various discussions with Dev around this & have requested that the ReadMe & help be updated. There may still be a performance benefit for iParts/iAssemblies if that variable is set & we couldn't find any major downsides from leaving it in place.

In terms of can we do anything more to improve the performance of Excel based interactions; that's the bigger project I mentioned. There's a general desire to move away from Excel but that's all still under investigation for the future.

Thanks

Chris