CAD/CAM discussion forum > CAD > Small Bug with ctb folders

Small Bug with ctb folders

    
  Subscribe Topic

Rank: 1

jcm1961

Newbie

posts: 5

Registered: 2014-1-8

Message 1 of 4

 Small Bug with ctb folders
11-05-2018 08:15 . pm   |   View his/her posts only
VERNUM = "2018.03.16(29562)_x64"

We detected a small bug with the ctb destination folder "printer style Table Search Path".
When we use a folder with subfolders in it with more ctb, the ctb don't work properly when you print.
It works fine when you use a folder with no subfolders in it works fine.

Hope you can fix it...

Rank: 5Rank: 5

ZWCAD_Support

posts: 138

Registered: 2016-4-14

Message 2 of 4

14-05-2018 11:21 . am   |   View his/her posts only
Reply 1# jcm1961


Hello, Thanks for your feedback.
We tried to reproduce this problem but could not get the result. Is there any special character included in the path? And can you confirm whether the path is set correctly in the options dialog box?

1.png
7 DayBefore 11:20
2.png
7 DayBefore 11:20

Rank: 1

jcm1961

Newbie

posts: 5

Registered: 2014-1-8

Message 3 of 4

15-05-2018 04:25 . pm   |   View his/her posts only
Here are the steps to reproduce de bug...

First, without subfolders (everything Works fine..)
Step 1

Step 1

Untitled-1.jpg
6 DayBefore 16:18


Step 2

Step 2

Untitled-2.jpg
6 DayBefore 16:18


Step 3

Step 3

Untitled-3.jpg
6 DayBefore 16:18


Step 4

Step 4

Untitled-4.jpg
6 DayBefore 16:18



And now with subfolders (note: we have more tan 100 sub folders with more tan 1000 ctb in it)

Step 2.1

Step 2.1

Untitled-2.1.jpg
6 DayBefore 16:18


Step 2.2

Step 2.2

Untitled-2.2.jpg
6 DayBefore 16:18


Step 2.3 (Error)

Step 2.3

Untitled-2.3.jpg
6 DayBefore 16:18


Step 2.4 (Wrong result ctb not working, lines in color...)

Step 2.4

Untitled-2.4.jpg
6 DayBefore 16:18



hope this can helps!

Rank: 5Rank: 5

ZWCAD_Support

posts: 138

Registered: 2016-4-14

Message 4 of 4

16-05-2018 02:21 . pm   |   View his/her posts only
Reply 3# jcm1961


Hi
Thanks for your detailed description, it is quite clear. However we tried to reproduce with our files here but still could not confirm it. Have you tried to change the folder path? For example, change F: to C:, will the problem persist?
See also
X