Fragile release 2.6.3.182

15 views
Skip to first unread message

C Burch

unread,
Feb 9, 2011, 7:28:32 PM2/9/11
to log...@googlegroups.com
This latest release is a pretty significant revision - enough that the
next release will probably be labeled "2.7.0" rather than "2.6.3,"
though I hope to add in some more revisions to that. This includes the
transistor, transmission gate, power, and ground components based on a
library contributed by T. Cruz (who's supporting the Portuguese
translation). I have to admit that I did a *lot* of tweaking to his
code, both for aesthetic appeal and to add new features like multibit
operation, so any errors that are there now are probably from what I
did. Anyway, here's a full rundown of the changes:


Feature: Added a Wiring library containing transistor, transmission
gate, power and ground components. Also, the splitter, pin, probe,
tunnel, clock, pull resistor, and bit extender were moved into the
Wiring library from the Base library, and constant was moved into the
Wiring library from the Gates library.

Feature: In the Combinational Analysis module, the user can select
between using a sum of products or a product of sums.

Bug fix: Changing the label for a Tunnel would not immediately affect
the values propagated through the circuit.

Bug fix: In the Karnaugh maps drawn by the Combinational Analysis
module, each implicant was indicated by a red rectangle, but they were
meant to use varied colors.

Design change: Added a "Close" item to the Window menu, which closes
the current window. The "Close" item in the File menu continues to
close the current project; its shortcut is now Control-Shift-W.

Design change: For the Memory library's Random component, a reset when
the seed is 0 computes a new initial seed based on the current time.
(It previously reset to the initial seed for the current simulation.)


I anticipate 2.7.0 will come in a week or so - probably without any
changes that are as radical as this one.

-Carl

C Burch

unread,
Feb 10, 2011, 8:21:33 AM2/10/11
to log...@googlegroups.com
Incidentally, this latest revision probably ends up making it so I'd
want to redo some screenshots. I'm holding off on redoing those,
though, because I'm planning some other revisions in the coming week
that would just invalidate those screenshots. -Carl

Ilia Lilov

unread,
Feb 10, 2011, 8:55:52 AM2/10/11
to log...@googlegroups.com
Hello, all!

Carl, I'm very glad you've been working on new releases so actively again!
I've done with translating all the new strings and texts in the
documentation. As of screenshots, I've got another one suggestion
affecting appearance before redoing screenshots. Some of the tool
icons have different orientation, so alignment of those pictograms is
very ugly somewhere. I've attached two pictures with red lines
underlining those places (somewhere it's good to have alignment along
center and somewhere along left side). If you're agree, Carl, I could
remake those icons a bit to fix alignment. I have a lot of spare time
now and you know, I like to fiddle with pictures.

Legacy library is trashed out now, but it is still presented in
documentation. May be it's worth to delete those pages too?

Little bug: try to connect Power or Ground component oriented east
face to face (without wires) with output of some components
(flip-flops, counters, etc.). Message "Conflicting component already
there" will appear. It behaves the same if you will try to connect
Power or Ground component with any facing face to face with any
component which has Facing attribute. But somehow it's OK to connect
Power or Ground component oriented west face to face with input of a
counter.

Ilia.

BadAlign-horizontal.png
BadAlign-vertical.png

C Burch

unread,
Feb 10, 2011, 9:46:42 AM2/10/11
to log...@googlegroups.com
Ilia, feel free to have a go at editing the icons so that they align
horizontally and vertically.

The Legacy library remains supported - it's just not loaded by
default. However, it's safe to say that nobody has worried about 1.0
compatibility for several years, so I'm happy to delete it. It does
simplify things slightly. Thanks for the suggestion.

I don't regard the "bug" you mention as a bug. Logisim intentionally
prevents you from placing two "outputs" (that is, a point where a
component feeds a value into the circuit layout) at the same location,
since this is almost inevitably a bug. Thus, you can't place a
constant 1 (a Power component) on top of the output of another
component: Whenever the component ends up with an output of 0 at any
point, you'll get an error value - which you shouldn't intend. (Note
that you're still allowed to attach a constant 1 to a multiplexer
output - as long as you have a short wire between them, so that the
red error value can be displayed.) It's entirely possible you would
want to do the same with an input, though, so that is allowed.

If you can suggest a very realistic situation where one would want to
attach two component outputs in at the same location, I'm open to
discussing changing it. It would need to be realistic enough, though,
to override the fact that some error reporting is useful for beginners
to circuit design who may not know any better.

-Carl

> --
> You received this message because you are subscribed to the Google Groups "Logisim" group.
> To post to this group, send email to log...@googlegroups.com.
> To unsubscribe from this group, send email to logisim+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/logisim?hl=en.
>
>

Ilia Lilov

unread,
Feb 10, 2011, 11:06:25 PM2/10/11
to log...@googlegroups.com
Carl, I'm sorry about my stupid "bug report" of "conflicting
components" message. It was obvious, but I was too lazy to think
enough.

I started to work on icons, but now I'm confused: documentation pages
use icons from resources/logisim/icons directory and it's OK. But
program GUI obviously also has some other source of icons: all the
flip-flops, RAM, ROM, and Menu Tool icons within toolbar and explorer
pane have icons which aren't the same with corresponding icons in
resources/logisim/icons (this is true since 2.6.3.182 except for Menu
Tool icon). Where can I find those icons to edit and is it good to
have different sources of icons? Also, icons for Constant and Pin
components within GUI are runtime generated depending on Data Bits
attribute of corresponding tool. Are they generated completely by code
or they also use icons as background?
Also, there are three icons in resources/logisim/icons which aren't in
use and could be deleted: dff.gif, drawarc.gif, drawpin.gif.

Ilia.

C Burch

unread,
Feb 10, 2011, 11:52:23 PM2/10/11
to log...@googlegroups.com
Actually, the documentation pages get the icons from doc/en/icons,
while the program draws from resources/logisim/icons. They are
supposed to be the same. It's a bit weird to have duplicate
directories, but they don't take much room, and it simplifies setting
things up for Eclipse and for documentation editing to have them
duplicated. If you rearrange them so that they're the same, that would
be welcome - I'd suggest using the versions from
resources/logisim/icons as the "master" copy.

I agree that dff.gif, drawarc.gif, and drawpin.gif aren't being used,
and they can safely be deleted. Actually, pinOutputReversed.gif isn't
used anywhere except in the documentation pages, but I recommend
keeping it in both locations so that they are consistent.

Several icons are generated by code rather than using the
corresponding icon files. That would include the flip-flops, RAM, ROM,
and Menu Tool. This is an artifact of how I was programming in earlier
versions of Logisim, where I tried to stay away from using GIF files
so Logisim would be usable in even if the GIF files can't be found;
that day has long past, so I'll switch them over to use the GIF files
instead. Actually, even today, it uses the GIF files at first - but
once you begin to use the tool, the icon switches over to drawing the
icon through code.

The program uses pinInput.gif and pinOutput.gif, painting the bit
width on top of them. The constant.gif icon is used only at the
beginning - once you begin to use the Constant tool, it starts drawing
the icon using its own code instead. Of course, constant.gif is needed
anyway for the documentation.

Ilia Lilov

unread,
Feb 11, 2011, 1:46:04 AM2/11/11
to log...@googlegroups.com
Thank you for explanation, Carl, but I still can't clarify situation
with flip-flops, RAM and ROM icons. They had changed since 2.6.3.182,
and it's a reason why I noticed bad alignment (these six icons stand
out against a background very much). Did you change them in this
fragile version? I can't find image files corresponding to them, so I
can't fix alignment.

Ilia.

Ilia Lilov

unread,
Feb 11, 2011, 4:05:49 AM2/11/11
to log...@googlegroups.com
I've found some kind of bug (I'm not sure). While exporting an image,
if "Printer View" option is chosen, Logisim draws every element in
black-and-white mode, even if element has a certain non-black color.
But some parts of Pull Resistor still light- or dark-green on
resulting image file.

Ilia Lilov

unread,
Feb 12, 2011, 1:35:50 AM2/12/11
to log...@googlegroups.com
Carl, those screenshots demonstrating bad icons alignment were made by
me under Debian GNU/Linux, but just now I rebooted under Windows XP
and realized there is almost perfect icons alignment while using WinXP
and its JRE. So, my idea to fix icons is pointless: alignment depends
on system. Moreover, under WinXP there is no difference between
flip-flops, RAM and ROM icons within GUI between 2.6.3.182 and
previous 2.6.3.177 versions. So, I think you could check what's wrong
with the recent 2.6.3.182 version under GNU/Linux.

Uwe Zimmermann

unread,
Feb 14, 2011, 11:52:51 AM2/14/11
to C Burch
Hello all!

I just wanted to let you know that I am still around and will continue
with the German translation as soon as possible, but not before it is
worth while. I am currently still quite busy and haven't spent too
much time with Logisim for many weeks now...

Uwe.

Reply all
Reply to author
Forward
0 new messages