To Sourceforge Cedar support -- This is the second time I've suggested the following. Transfer all open Sourceforge tickets to your new GitHub support site, then close them all here. Change the project description here in Sourceforge to say "This site is OBSOLETE and exists only to point you to the current support site at ... (GitHub site)". As you can see on this issue, Antonio Abarca posted a comment here 2020-03-28, thinking that this site is being used for Cedar support when it isn't any lon...
To Sourceforge Cedar support -- This is the second time I've suggested the following. Transfer all open Sourceforge tickets to your new GitHub support site, then close them all here. Change the project description here in Sourceforge to say "This site is OBSOLETE and exists only to point you to the current support site at ... (GitHub site)". As you can see on this issue, Antonio Abarca posted a comment here 2020-03-28, thinking that this site is being used for Cedar support when it isn't any lon...
To Sourceforge Cedar support -- This is the second time I've suggested the following. Transfer all open Sourceforge tickets to your new GitHub support site, then close them all here. Change the project description here in Sourceforge to say "This site is OBSOLETE and exists only to point you to the current support site at ... <github site="">". As you can see on this issue, Antonio Abarca posted a comment here 2020-03-28, thinking that this site is being used for Cedar support when it isn't any ...
Dear Rick, I use W10 and I have too your problem. I,ve tried to fix opening the program as administrator. At the moment it´s running ok. Regards,
Loading a large design causes cedarlogic to crash
Unless this is re-experienced I think it's too old to be worth porting over to github. Will close and assume fixed.
status: open --> closed-fixed
More Info on failed screen redraw
excess connection "dots"
Picked up here: https://github.com/CedarvilleCS/CedarLogic/issues/17
Picked up here: https://github.com/CedarvilleCS/CedarLogic/issues/16
Picked up here: https://github.com/CedarvilleCS/CedarLogic/issues/18
Picked up here: https://github.com/CedarvilleCS/CedarLogic/issues/19
Picked up here: https://github.com/CedarvilleCS/CedarLogic/issues/20
Also, I've created a ticket for this here: https://github.com/CedarvilleCS/CedarLogic/issues/11
Hi Rick, Thank you for the question and suggestion, I agree dual sites is not a good idea and I'm just finishing copying the open tickets over to GitHub so we can close these. I agree that I'd like to make this a redirection to GitHub but that may not happen just yet. I'm hearing conflicting reports about how buggy v2.3.5 is on GitHub so kshomper, the professor who just handed this over to me, may want to leave this up until GitHub is stabalized. Here is the follow-up issue on GitHub for this one....
Here's the follow-up issue: https://github.com/CedarvilleCS/CedarLogic/issues/25
I've picked this up here: https://github.com/CedarvilleCS/CedarLogic/issues/24 We'd have to think through the GUI implications.
Hi Gary, you may be interested to know that the source is availible now under GNU v3.0 and actively maintained. I've made issues for your requests which I'm linking below: - https://github.com/CedarvilleCS/CedarLogic/issues/21 - https://github.com/CedarvilleCS/CedarLogic/issues/22 - https://github.com/CedarvilleCS/CedarLogic/issues/23
Hi Gary, you may be interested to know that the source is availible now under GNU v3.0 and actively maintained. I've made issues for your requests which I'm linking below: https://github.com/CedarvilleCS/CedarLogic/issues/21 https://github.com/CedarvilleCS/CedarLogic/issues/22 * https://github.com/CedarvilleCS/CedarLogic/issues/23
Oh, that's not good - picked up here: https://github.com/CedarvilleCS/CedarLogic/issues/15
Picked up here: https://github.com/CedarvilleCS/CedarLogic/issues/14
Picked up here: https://github.com/CedarvilleCS/CedarLogic/issues/13
Haha, I have no idea how to close something on this platform
I doubt this is still a concern. * status: open --> closed
I doubt this is still a concern. - Status: open --> closed
Picked up here: https://github.com/CedarvilleCS/CedarLogic/issues/8
Picked up here: https://github.com/CedarvilleCS/CedarLogic/issues/12
This has been picked up here: https://github.com/CedarvilleCS/CedarLogic/issues/11
Picked up here: https://github.com/CedarvilleCS/CedarLogic/issues/10
The end state isn't clear from reading this thread, a ticket has been created here to discover what if anything need be done.
Feature ticket moved to GH version of CedarLogic. Ticket may be closed.
https://github.com/CedarvilleCS/CedarLogic/issues/6
Feature ticket replicated at GitHub site so this one can be closed whenever an admin gets around to it (or I become an admin)
https://github.com/CedarvilleCS/CedarLogic/issues/5
https://github.com/CedarvilleCS/CedarLogic/issues/4
I like this idea. Am adding a feature ticket for it at the new project site: https://github.com/CedarvilleCS/CedarLogic
This appears to be fixed by v2.3.5. Anyone mind if I close this?
Hi Joseph, Thank you for Cedar and I am pleased to hear further development is planned. I am currently teaching Digital Logic for the 4th time at a local community college and all my students have Cedar v1.5 on their laptops. Question and a suggestion: Do you want a new Issue on Github? If you are switching to support there, I suggest copying over all open Tickets from Sourceforge and closing them here, then leaving the Sourceforge site with only a re-direction to Github. I think the existence of...
Hi Joseph, Thank you for Cedar and I am pleased to hear further development is planned. I am currently teaching Digital Logic for the 4th time at a local community college and all my students have Cedar v1.5 on their laptops. Question and a suggestion: Do you want a new Issue on Github? If you are switching to support there, I suggest copying over all open Tickets from Sourceforge and closing them here, then leaving the Sourceforge site with only a re-direction to Github. I think avoiding the existence...
Hi Rick, As I'm running through these old tickets I'm glad to see you're still using CedarLogic. Yes, we can look at fixing that. Development is continuing here: https://github.com/CedarvilleCS/CedarLogic
Hi Jacob, That's an interesting idea - I'll add a CR for that at the new project site: https://github.com/CedarvilleCS/CedarLogic
Hi Roman Hocke, That feature has been added to a later version hereto only availible internally because it's buggy. As the project has just been open sourced here: https://github.com/CedarvilleCS/CedarLogic my first priority as the maintainer will be to get the bugs out so you can enjoy this feature bug-free. Joe
Hi Rick, Is this a change request requesting SPDT and DPDT switches? It not immediately clear to me what you're asking. If you want to fill out a CR here: https://github.com/CedarvilleCS/CedarLogic we're continuing the project on GitHub
Hi Yossi, Long story short we actually have that feature partly built in a later version of the product. It's just gone open source development will be continuing here: https://github.com/CedarvilleCS/CedarLogic If you'd like to submit a feature request there we can move forward. Thanks for your help! - Joe
Cedar opens off-monitor, so invisible
I am doing a research project for which i need to do some modification in CEDAR Logic....
Cedar logic sim and componenets
SPDT "3-Way" and DPDT "4-Way" Switches
Hello, nice software, but there are a few places where improvments would increase...
I'm trying to edit the lib file. I'm doing this after I close the simulator [and...
Wanted to say that this is a job well done I'm currently using this to simulate some...
Hey Lovely software. Has anyone thought of how a generic monostable multivibrator...
Hey Lovely software. Has anyone thought of how a generic monostable multivibrator...