Eureka 1.00 Released!

[andrewj]

1. Version number is shown in the window's title, though I agree should be inside the window too.

2. the toolkit I am using, FLTK, does not make it easy to increase the font size over the whole program, because all widgets are positioned by exact pixel coordinates. On old monitors (like mine), with a resolution like 1024x768, the font is legible, but I guess on modern machines with resolutions like 1920x1280 the font would be very small. (FWIW it is actually bigger than the FLTK default font size). Other aspects of the UI may be too small too.

I would like to fix this, but making every part of the UI able to support different font sizes (etc) is a lot of work, so I'm not sure that will happen.

If I drop support for 800x600 resolutions (make 1024x768 the minimum resolution), then I could make the font a bit bigger (and bolder) and it will be more readable on 2K resolution monitors.

The color scheme can be changed in the Preferences dialog, as well as the general appearance of FLTK widgets.

3. Some tools that exist in Yadex are not implemented yet -- stair building is one of them. Other tools are very keyboard focussed and not available in the GUI anywhere -- e.g. you can align textures in the 3D view by positioning the mouse on the line and pressing 'x' or 'y' keys (with SHIFT key to change alignment focus to the right side instead of left side).

I am planning a context menu and/or a toolbar for such tools.

4. Textures are arranged as Lower / Rail / Upper, but with a twist that on one-sided lines, the middle texture appears in the left spot. I did this so you can safely select a group of lines where some are one-sided and some two-sided, and change the texture (the old way often lead to accidentally setting mid textures on two-sided lines when you did not want it).

If I increase the minimum resolution requirement, I may rearrange the textures vertically so that Upper is on top, Rail is middle, and Lower/Mid is on the bottom.

5. Some BOOM features, especially generalized line and sector types, are not supported yet.

6. A few days ago I found a bug with the sector mismatch check -- I have a test case and will fix it soon.

[wesleyjohnson]

I use an IBM G96 color graphics monitor running at 1600x1200.
I cannot check what is in Eureka preferences right now because that would involve a different computer running Linux 2.6, so I am going by memory.

Font size: The size would be adequate if there was more contrast.
An increase of font size also increases menu sizes and control arrangements.
Having some user control would be best.
Is there a default font for fltk that could get a font size control ??

Font color: The thin font makes the letters hard to read, especially on a tan background. It is only 1 pixel wide and it is black against a tan background. Please consider making black the default background, or a much darker tan with light colored text. Because of light bleeding, it is much easier to see a bright thin font line against black, than it is to see the same size black line against white. I will have to look in the preferences to see if such a thing could be done there. But for new users, it the defaults should have much stronger contrast, without having to configure the whole preferences color section to get it.

Style: The JED text editor has a top-level menu selection for style, to which I added a green-text-on-black style. There generally are three styles needed in such menus.
Black text on off-white background,
White text on black background,
Custom (odd colors on odd backgrounds).
The fourth standard is green text on dark background, which is easiest on the eyes because we have more eye sensors for green than any other color.

Bold Font: For small font sizes, selecting a bold font instead improves the readability. For all menus, selecting a thicker font, or a bold version of a font, may work best, even for 1024x768.
Use a different font, or turn Bold off, for any large text.

Tan background: I think this causes the most problems because it is so neutral that the font does not stand out well. I will look to see if this be changed to black in the preferences.

[Yokai]

Just hanging around to ask Andrew if something is going to happen around...

[hawkwind]

All Things in the map are flagged dm and coop, but that obviously is not the case.

[andrewj]

hawkwind said:

All Things in the map are flagged dm and coop, but that obviously is not the case.

Vanilla DOOM only has a "multiplayer" flag.

BOOM then renamed it "NOT_SP", and added "NOT_COOP" and "NOT_DM" flags.

Eureka shows the opposite of the Boom flags, i.e. "sp", "coop" and "dm", because I think that is more intuitive for users.

For Vanilla DOOM, maybe it should only show a single flag (and not show the "friend" flag either, as it is an MBF extension only some source ports support). Need to think about it.

[hawkwind]

You misunderstand me. Open up doom2.wad > Mode > Things. ALL the Things are flagged coop and dm. This is incorrect.

Also, notice that for Boom, DB2 has multiplayer (dm?), not coop and not deathmatch flags all together, not a rename.

[Gez]

Since vanilla Doom does not have "not coop" and "not DM", it's normal that all things are implicitly flagged as "also coop" and "also DM". The only thing that you can do is uncheck "single player" which means setting the "multiplayer only" flag.

What Eureka does is normal and correct, based on the decision to show negative flags as positive choices. The absence of a negation is an implicit affirmation.