Custom Query (27 matches)
Results (10 - 12 of 27)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #46 | fixed | Text does not wrap properly for DBCS | ||
| Description |
DBCS systems have problems with text wrapping. This apparently makes New View nearly unusable on these systems. Alex can provide some examples. |
|||
| #47 | worksforme | Persistent startup crash when NetDrive control program is active | ||
| Description |
I finally chased this one down and figured out why it was coming and going. Issue: When ndctl.exe (the NetDrive daemon) is running and the following plugins are loaded:
upon starting NewView, the following crash is reported and recorded: App Version: V2.19.4 Components Version: v1.11.26 Library Version: V1.5.14 Running as process: C:\ECS\BIN\NEWVIEW.EXE 31 January 2017, 20:39:04 Exception type: EGPFault Description: Access violation exception (EGPFault) occured at CS:EIP =$0000005B:$000E5B67 Location: $000E5B67 Callstack: $00010740 System version:20.45.0 OS/2 4.5 RAM: 1982 MB Boot drive: C Video resolution: 1400x1050 Color depth: 32 bits Video driver: GRADD: SDDGRADD,WOVERLAY Loaded files (2): Further, when selecting No (do not exit the program) following the startup crash, and subsequently searching all help files, attempting to open the directory selection window fails (this is what put me onto NetDrive in the first place). I suspect it is the Samba plugin, as that is the plugin currently seeing most development activity, and this issue did not occur until I was in the middle of testing new Samba builds. I will confirm by disabling Samba and rebooting. |
|||
| #49 | fixed | When one instance of NewView is open on one virtual desktop, new instance should be opened on current one | ||
| Description |
NewView needs to be made XPager-aware. That is to say that when it has been launched on Desktop 1, and the user switches to Desktop 5, opens an application, and selects Help, NewView should open on the current desktop (5, in this case), and not cascaded with the first instance on Desktop 1. I realize that this may actually be something for XPager to handle, and we can surely reference this ticket from the xTracker. |
|||
