No matter what actual value I put for a crystal (e.g.,115 MHz), it always goes back to 10 MHz when I save. I'm using Mozilla Firefox for my browser. Is there anything I can do to fix this? Thank you. |
by lanbergld
June 09, 2013 |
Same in Chrome. Please post a BUG REPORT: https://www.circuitlab.com/forums/support/topic/8s9n9hav/how-to-use-the-circuitlab-support-forum/ |
by signality
June 09, 2013 |
Thank you. |
by lanbergld
June 09, 2013 |
YET happening... 90 day after first report: No matter what actual value I put for a crystal (e.g.,3.5 MHz), it always goes back to 10 MHz when I save - printing does not show the values entered also. I'm using Chrome Version 29.0.1547.62 m for browser - updated by now. Is there anything you will do to fix this? I am still trying the software as trial period is too short. Then I paid the cheaper version to make a longer trial. Is anything wrong with the browser? Can you help on this at all? thanks. |
by ehisatugo
September 03, 2013 |
It probably won't get fixed until ... Please feel free to. :) |
by signality
September 03, 2013 |
I'm going to second this fix, I'm a few months away from printing a thesis with some circuit diagrams in it so I have enough problems with out having to edit the PNG. I have Fire Fox 23.0.1 |
by Garrett
September 04, 2013 |
(Sigh) "If you want owt doin', do it theself" |
by signality
September 04, 2013 |
Hey, signality: As a member of the development team you would be concerned about a bug report like these one. If you are saying that your company will not fix this and is telling us to make ourselves, then there is only one way out: to get rid of this poor software and stuck to "tiny circuit". I think you are behaving bad and your company also, as represented by you. This software is almost loosing my trial to trash. |
by ehisatugo
September 04, 2013 |
This issue is now fixed in the latest version of CircuitLab. Please reload your CircuitLab window and save your circuit. You might need to actually move an element to force the renderer to re-render your circuit. |
by hevans
September 04, 2013 |
Thanks Hevans. Testing will keep going... |
by ehisatugo
September 05, 2013 |
Sorry but you are complaining to entirely the wrong person. As a quick check of my CL profile would confirm, I have no connection with CL. I just hang around here to help out. Moreover since, in the 3 months or so since this bug was pointed out, it was not until I posted a bug report - after twice gently suggesting that others could do so - that anything happened about it, I therefore consider that you are somewhat at risk of biting the hand that feeds you. :( |
by signality
September 05, 2013 |
I think this was fixed anyway. What do you mean as you post the bug report?? I was sure this post is for this bug report and I added some information requested on that link you post. The bug report was posted at the first post, 3 month or so, as CL stated this forum is the right place to do so. I do not think people here are supposed to get your comment "If you want owt doin', do it theself" in a good sense when we are asking to developers to do something about a bug. In occasions like this one, plain English would avoid this misunderstanding, as users here often do not have English as second, third or Nth language as me. My English is poor, as I learned it for myself, without a school. Several others did so as I believe. Sorry for bite. Regards. Euclides. |
by ehisatugo
September 05, 2013 |
This first post: was a request for help, not a formal bug report. CL asks that if you want to post a bug report, to do this: https://www.circuitlab.com/forums/support/topic/8s9n9hav/how-to-use-the-circuitlab-support-forum/ As far as I could find out, nobody posted a formal bug report about this (I searched the CL forums for one). I twice suggested that people posting about the bug post a formal bug report: and Still nobody took the hint posted a formal bug report. So because no-one else seemed to want to make the effort, I posted a bug report myself: And then just over 3 hours later, the guys at CL fixed the bug. That is why they ask for formal bug reports. They do not have time to read through every support request on the forum. They expect people taking part on the forum to help each other and not rely on them having to deal with every little request. However, if there's a bug then posting a bug report makes them sit up and take notice and do something about it. Forgive my lapse into colloquial Yorkshire dialect. You will see from my other posts on CL posts that most of the time I do try to use plain English. This was one occasion that I felt it reasonable to express my feeling that people seemed a little unwilling to help themselves. :) |
by signality
September 05, 2013 |
Oh, got it. One doubt remains: How can one differentiate from a bug report or a support help?? I did read the text at https://www.circuitlab.com/forums/support/topic/8s9n9hav/how-to-use-the-circuitlab-support-forum/ many times... and did not found any clue to get this. I think many others don't also. Is it just the "subject" of the post? I think they could let it more explicit. Anyway, thanks for make this clear to us. Cheers. Euclides. |
by ehisatugo
September 05, 2013 |
Please sign in or create an account to comment.
CircuitLab is an in-browser schematic capture and circuit simulation software tool to help you rapidly design and analyze analog and digital electronics systems.