Support Forum
fSelect( ) function doesn't select the correct box
User
LayoutEditorFull
Thursday 2nd May 2019
Attachments:
(only for registered users)
select_bug1.gds
Please execute the attached macro on the GDS file. You can see the first fSelect() function selects the box added on layer-1 and the following punchWithSelection() erases everything inside the box. The same method is used again to erase the elements inside the right box, but the result is different. Obvious the second fSelect() function cannot select the box even when the point of selection is a corner of the added box. I believe this is a bug of fSelect() function. My Layout Editor version is 20190401. Please correct this bug. Thanks!
LayoutEditorFull
Thursday 2nd May 2019
Attachments:
(only for registered users)
select_bug1.gdsPlease execute the attached macro on the GDS file. You can see the first fSelect() function selects the box added on layer-1 and the following punchWithSelection() erases everything inside the box. The same method is used again to erase the elements inside the right box, but the result is different. Obvious the second fSelect() function cannot select the box even when the point of selection is a corner of the added box. I believe this is a bug of fSelect() function. My Layout Editor version is 20190401. Please correct this bug. Thanks!
Jürgen
LayoutEditorFull
Thursday 2nd May 2019 Can you also send the macro code to reproduce this issue? fSelect() will select the shape nearest to the previous entered point. If there is any other shape closer to the entered point, the right box will not be selected.
LayoutEditorFull
Thursday 2nd May 2019 Can you also send the macro code to reproduce this issue? fSelect() will select the shape nearest to the previous entered point. If there is any other shape closer to the entered point, the right box will not be selected.
User
LayoutEditorFull
Saturday 4th May 2019 Here is the macro. Somehow it cannot be attached as a file. !/usr/bin/layout #name=select_bug1 int main() { string f1_name="select_bug1.gds"; layout->open(f1_name); layers::enableAllLayer(); layout->drawing->activeLayer=1; layout->drawing->p(-185, -545); layout->drawing->p(-100, -300); layout->drawing->box(); layout->drawing->p(-185, -545); // <---- this point allow fSelect() to select the box correctly layout->drawing->fSelect(); layout->drawing->currentCell->punchWithSelection(); layout->drawing->p(430, -545); layout->drawing->p(350, -300); layout->drawing->box(); layout->drawing->p(430, -545); // <---- this point doesn't allow fSelect() to select the box!!!??? layout->drawing->fSelect(); layout->drawing->currentCell->punchWithSelection(); }
LayoutEditorFull
Saturday 4th May 2019 Here is the macro. Somehow it cannot be attached as a file. !/usr/bin/layout #name=select_bug1 int main() { string f1_name="select_bug1.gds"; layout->open(f1_name); layers::enableAllLayer(); layout->drawing->activeLayer=1; layout->drawing->p(-185, -545); layout->drawing->p(-100, -300); layout->drawing->box(); layout->drawing->p(-185, -545); // <---- this point allow fSelect() to select the box correctly layout->drawing->fSelect(); layout->drawing->currentCell->punchWithSelection(); layout->drawing->p(430, -545); layout->drawing->p(350, -300); layout->drawing->box(); layout->drawing->p(430, -545); // <---- this point doesn't allow fSelect() to select the box!!!??? layout->drawing->fSelect(); layout->drawing->currentCell->punchWithSelection(); }
Jürgen
LayoutEditorFull
Sunday 5th May 2019 Thanks for reporting this issue. It will be fixed with the next update. The problem will only occur when you use the low right point of a box. If you do a fSelect on point (350,-545) the problem will not occur. For your application i would recommend to use `layout->drawing->currentCell->firstElement->thisElement->selectAll(); ` instead of the fSelect(). It will select the last added shape. As it does not require any search on the nearest shapes, it will be faster.
LayoutEditorFull
Sunday 5th May 2019 Thanks for reporting this issue. It will be fixed with the next update. The problem will only occur when you use the low right point of a box. If you do a fSelect on point (350,-545) the problem will not occur. For your application i would recommend to use `layout->drawing->currentCell->firstElement->thisElement->selectAll(); ` instead of the fSelect(). It will select the last added shape. As it does not require any search on the nearest shapes, it will be faster.
User
LayoutEditorFull
Thursday 9th May 2019
LayoutEditorFull
Thursday 9th May 2019
User
LayoutEditorFull
Thursday 9th May 2019 OK. My license to update the Layout Editor ends on 6/4. Hope you'll be able to release next update soon. Thanks!
LayoutEditorFull
Thursday 9th May 2019 OK. My license to update the Layout Editor ends on 6/4. Hope you'll be able to release next update soon. Thanks!
Jürgen
LayoutEditorFull
Thursday 9th May 2019 The next regular release will not ready until June 4th. However as soon the development release having that fixed is available, i will post its download link here.
LayoutEditorFull
Thursday 9th May 2019 The next regular release will not ready until June 4th. However as soon the development release having that fixed is available, i will post its download link here.
Jürgen
LayoutEditorFull
Friday 10th May 2019 Here is the link: [http://layouteditor.com/releases/layout-20190509-win-64bit-installer.msi](http://layouteditor.com/releases/layout-20190509-win-64bit-installer.msi) Installed it shows the wrong version month, but that is real dated 20190509 and should fix the problem with fselect()
LayoutEditorFull
Friday 10th May 2019 Here is the link: [http://layouteditor.com/releases/layout-20190509-win-64bit-installer.msi](http://layouteditor.com/releases/layout-20190509-win-64bit-installer.msi) Installed it shows the wrong version month, but that is real dated 20190509 and should fix the problem with fselect()
User
LayoutEditorFull
Monday 20th May 2019 OK. My license to update LayoutEditor exactly ends on June 4th. Will I still be able to install the upcoming regular release on 6/4 if you do post this update on 6/4?
LayoutEditorFull
Monday 20th May 2019 OK. My license to update LayoutEditor exactly ends on June 4th. Will I still be able to install the upcoming regular release on 6/4 if you do post this update on 6/4?
Jürgen
LayoutEditorFull
Tuesday 21st May 2019 Yes it would, even if the release would be published on 6/5. It is ensured that a new published release of the LayoutEditor can be used on every system having maintenance during the minute of post of the update. The different time zones in the world will result that in most countries the update can be installed one or two days after the maintenance expiration would allow.
LayoutEditorFull
Tuesday 21st May 2019 Yes it would, even if the release would be published on 6/5. It is ensured that a new published release of the LayoutEditor can be used on every system having maintenance during the minute of post of the update. The different time zones in the world will result that in most countries the update can be installed one or two days after the maintenance expiration would allow.