Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resize stripboard is adding strips the wrong way #2998

Closed
aknoerig opened this issue Sep 23, 2014 · 8 comments
Closed

Resize stripboard is adding strips the wrong way #2998

aknoerig opened this issue Sep 23, 2014 · 8 comments

Comments

@aknoerig
Copy link
Contributor

From Martin.B...@gmail.com on September 10, 2014 16:45:22

What steps will reproduce the problem? 1. Drag a stripboard to Breadboard view
2. Resize it to e.g. 30 x 30 (becomes very slow)
3. Original stripboard looks fine, the added holes are not stripboard Attach your sketch file and/or custom part files to the bug report. What is the expected output? What do you see instead? Expected output is a larger stripboard. Looks like added holes are added the wrong way What version of Fritzing are you using? On what operating system? Version 0.9.0 (bda4e 2014-06-11) 64 [Qt 4.8.5] on Linux (PCLinuxOS 64 bit) Please provide any additional information below.

Attachment: Reed.fzz

Original issue: http://code.google.com/p/fritzing/issues/detail?id=2998

@aknoerig
Copy link
Contributor Author

From wuftymer...@gmail.com on September 18, 2014 07:34:10

Exact same issue.

Version 0.9.0 (bda4e 2014-06-11) 64 [Qt 5.2.1] Windows. 7 64 Bit

if you then change strip direction twice it sorts the problem with the extended area.

Sketch attached.

Attachment: Stripboard Issue.fzz

@GregWoods

This comment has been minimized.

@SilverNodashi

This comment has been minimized.

@failiz
Copy link
Contributor

failiz commented Mar 24, 2021

@SilverNodashi @GregWoods dead revive sometimes :-)
remove imported label, add stripboard label

@hxlnt
Copy link

hxlnt commented Jul 10, 2021

+1, please fix. (Are repo owners hiding user comments on this bug? If so--why?)

failiz added a commit to failiz/fritzing-app that referenced this issue Jul 11, 2021
…ritzing#2998 and fritzing#3084. The slow performance is still present but the extended area is not shortcircuited.
@failiz
Copy link
Contributor

failiz commented Jul 11, 2021

@hxlnt , the comments were out of topic, but owners are not hiding anything, you can press the button "Show comment" to see them.
In any case, I just pushed a fix for the issue. Lets hope that it is accepted and does not create new errors. Until is merged and there is a new release, you can see #3090 for a handy workaround.

@georgyfarniev
Copy link

The issue is still here, in 2021. Feels like fritzing is abandoned.

@failiz
Copy link
Contributor

failiz commented Aug 29, 2021

@georgyfarniev , Fritzing development was frozen for a few years and restarted two years ago.

This bug has been fixed, and it will be released in 0.9.9. If you are able to compile Fritzing, you can test the fix in my pull request. If not, check #3090 for a handy workaround.

KjellMorgenstern pushed a commit that referenced this issue Sep 24, 2021
#3084. The slow performance is still present but the extended area is not shortcircuited.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants