Opened 13 years ago

Last modified 5 years ago

#23 assigned defect

Aven 1.2.0 — at Version 3

Reported by: Brian Owned by: Olly Betts
Priority: minor Milestone:
Component: aven Version: 1.2.0
Keywords: Cc:

Description (last modified by Olly Betts)

Aven still does not work properly on my computer,an oldish Win 2000. As I did not like the new Aven much, it dos'nt matter much.

Windows 2000 (build 2195, Service Pack 4)
wxWidgets 2.8.10
Display Depth: 32 bpp (colour)
OpenGL 1.4 15.13.10.08
S3 Graphics, Incorporated
S3 Graphics DeltaChromeR8G8B8
Max Texture size: 2048x2048
Max Viewport size: 2048x2048
Smooth Point Size 0.500-64.000 (granularity 0.125)
Double buffered: true
WGL_ARB_extensions_string WGL_EXT_extensions_string GL_ARB_multitexture  GL_ARB_transpose_matrix  GL_ARB_texture_env_add  GL_ARB_texture_cube_map  GL_ARB_texture_compression  GL_ARB_texture_border_clamp  GL_ARB_point_parameters  GL_ARB_texture_env_combine  GL_ARB_texture_env_crossbar  GL_ARB_texture_env_dot3  GL_ARB_texture_mirrored_repeat  GL_ARB_depth_texture  GL_ARB_shadow  GL_ARB_shadow_ambient  GL_ARB_window_pos  GL_ARB_vertex_program  GL_ARB_fragment_program  GL_ARB_vertex_buffer_object  GL_ARB_occlusion_query  GL_ARB_texture_non_power_of_two  GL_ARB_point_sprite  GL_EXT_abgr  GL_EXT_blend_color  GL_EXT_texture3D  GL_EXT_histogram  GL_EXT_convolution  GL_EXT_packed_pixels  GL_SGIS_texture_lod  GL_EXT_rescale_normal  GL_EXT_vertex_array  GL_SGIS_generate_mipmap  GL_SGIS_texture_edge_clamp  GL_SGIS_texture_border_clamp  GL_EXT_blend_minmax  GL_EXT_blend_subtract  GL_EXT_point_parameters  GL_EXT_compiled_vertex_array  GL_EXT_draw_range_elements  GL_EXT_bgra  GL_EXT_separate_specular_color  GL_EXT_secondary_color  GL_EXT_multi_draw_arrays  GL_EXT_fog_coord  GL_EXT_texture_env_combine  GL_EXT_blend_func_separate  GL_EXT_stencil_wrap  GL_NV_texgen_reflection  GL_EXT_texture_env_add  GL_EXT_texture_lod_bias  GL_EXT_texture_filter_anisotropic  GL_NV_blend_square  GL_EXT_texture_compression_s3tc  GL_ATI_fragment_shader  GL_ATI_vertex_array_object  GL_EXT_vertex_shader  GL_ATI_element_array  GL_EXT_shadow_funcs  GL_EXT_stencil_two_side  GL_S3_s3tc  GL_ATI_texture_env_combine3  GL_ATI_vertex_attrib_array_object  GL_KTX_buffer_region  GL_WIN_swap_hint  GL_EXT_color_table  GL_EXT_color_matrix  GL_EXT_texture_cube_map  GL_EXT_texture_edge_clamp  

Change History (3)

comment:1 Changed 13 years ago by Olly Betts

In what ways doesn't it work properly?

And what don't you like about it compared to the old version?

Last edited 8 years ago by Olly Betts (previous) (diff)

comment:2 in reply to:  1 Changed 13 years ago by Brian

Replying to olly:

In what ways doesn't it work properly?

And what don't you like about it compared to the old version?

The colour by depth window has no text and there is an error message when you shut Aven down:- The instruction at "0x1009d117" referenced memory at "0x0000004c". The memory could not be "read". Click OK to terminate program

The old Aven used to zoom out to a 50CM bar across most of the screen, now it only zooms to a 2M bar a third of the screen. The labeling of the stations and the distance between is now on a small bar at the bottom of the screen and is dificult to see.

Last edited 8 years ago by Olly Betts (previous) (diff)

comment:3 Changed 13 years ago by Olly Betts

Description: modified (diff)

Do you see labels on the scale bar, compass, and clino? And do station names work (Ctrl+N to turn them on)? They're all drawn in the same way as the depth bar text so if the others work it's something that's different there that's causing the issue.

Not sure about the crash - I'll see if I can get Jenny to reproduce it at work.

I've increased the distance you can zoom in to match 1.0.x, and made the scale bar maximum length the same as it used to be in r3779, so those will be fixed in 1.2.1.

Putting the station details and distance in the status bar was a deliberate decision - it means you don't need the side panel open to see this information, which makes things much more usable on smaller screens, and it also gives more space for the survey tree. So undoing that change doesn't seem great.

In what way do you find it more difficult to see than before?

I've wondered if we could provide this information in a little tooltip-like window which could be shown near where you're measuring which might look better (and then we wouldn't need the status bar at all).

Note: See TracTickets for help on using tickets.