JosefNemec / LiteDbExplorer

Viewer and editor for https://github.com/mbdavid/LiteDB databases.
MIT License
218 stars 104 forks source link

Main Windows has OverPasses screen, no resizing possible on W10x64 dual screen PC #7

Closed andy-soft closed 7 years ago

andy-soft commented 7 years ago

Hi, I built the version and also tested it under Portable (binaries) the result is the same: no resizing, window maximized, something is not working in the Aero-UI screen.

JosefNemec commented 7 years ago

I'm not sure I understand what the problem is. Does it mean that program window always stays maximized and you can't resize it or restore it from maximized state? Does it happen right after start? Can you share some screenshots? I also have Win10x64 with two screens and I fail to reproduce anything like you describe.

andy-soft commented 7 years ago

Hi Josef & thanks for ur concern

I attach a ScreenShot done with ctrl+alt+print (but the actual window exceeds my screen and lacks the close icon, the margins to resize, etc., even it cannot be moved, only closed with alt+F4

I did not enter into the details as i don't know about this XAML formatting method for windows forms.

thanks!

PD: also I found this dbase very slow for inserting, I measured less than 500 insertions per second for simple dictionary word string (<20 chars length), a int a float and another 5 char string, very disappointing!

cheers!

my PC is VS 2015, win 10 x 64, dual core G2200 the main screen is 1680 x 1050 (20 inch) another secondary screen of 19 inch on the left, configures my simple & cheap development PC.

andres

On Tue, May 23, 2017 at 3:16 AM, Josef Nemec notifications@github.com wrote:

I'm not sure I understand what the problem is. Does it mean that program window always stays maximized and you can't resize it or restore it from maximized state? Does it happen right after start? Can you share some screenshots? I also have Win10x64 with two screens and I fail to reproduce anything like you describe.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/JosefNemec/LiteDbExplorer/issues/7#issuecomment-303300759, or mute the thread https://github.com/notifications/unsubscribe-auth/ANCPcXOqQWopT7FUHxxrUjmQOBmPUtILks5r8nnJgaJpZM4Nilq8 .

-- ing. Andrés T. Hohendahl director PandoraBox www.pandorabox.com.ar web.fi.uba.ar/~ahohenda

JosefNemec commented 7 years ago

OK, I see where the problem is, default window size is set to 1600x1000, which doesn't fit your resolution properly (counting in task bar and other UI controls). As a workaround you can use WinKey+ArrowUP key combination, which will maximize the window and you can then resize it as you wish. I will lower default windows size since this is obviously problem for these resolutions.

Regarding insert performance, ask on LiteDB's project page.

andy-soft commented 7 years ago

Perfect, thanks, I addressed the performance issue, had to insert multiple and commit at end, then the record write speed went up to 20k/second. Fine! thanks

On Wed, May 24, 2017 at 3:53 AM, Josef Nemec notifications@github.com wrote:

OK, I see where the problem is, default window size is set to 1600x1000, which doesn't fit your resolution properly (counting in task bar and other UI controls). As a workaround you can use WinKey+ArrowUP key combination, which will maximize the window and you can then resize it as you wish. I will lower default windows size since this is obviously problem for these resolutions.

Regarding insert performance, ask on LiteDB's project page.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/JosefNemec/LiteDbExplorer/issues/7#issuecomment-303634665, or mute the thread https://github.com/notifications/unsubscribe-auth/ANCPceP_ICKgMiblxDMd700RrPbtlxOPks5r89P6gaJpZM4Nilq8 .

-- ing. Andrés T. Hohendahl director PandoraBox www.pandorabox.com.ar web.fi.uba.ar/~ahohenda

andy-soft commented 7 years ago

Hi Josef

I corrected this, sniffed into the app. and it worked.

Have some comments to make some improvements.

the column names (bson names) at the top of the dataGrid, are ordered according their names, and this is sometimes bad, even should be draggable, persisting his selection in something like a property-record for each database opened, and probably persisted in a small "preferences" file on disk, indeed they should have initially the order given inside the database by the Bson serializer, which hopefully respects the creation/insertion order. ¿Am I wrong?) Actually I saw they are alphabetically ordered, this is bad for me.

The field names should allow an order, like most database managers do, allowing to sort (visually) by any of the fields, even is they are not on all records. (inexistence or null could be mapped as initial or empty field, or minus infinite as numerical, false as boolean, etc.)

Another tip is to allow filters on the top. not complex like SQL but simpler, perhaps some easy type of REGULAR Expressions with wildchars * and ?

If you point me where I can help on the source.

best regards

On Tue, May 23, 2017 at 9:39 PM, Andres Hohendahl < andres.hohendahl@gmail.com> wrote:

Hi Josef & thanks for ur concern

I attach a ScreenShot done with ctrl+alt+print (but the actual window exceeds my screen and lacks the close icon, the margins to resize, etc., even it cannot be moved, only closed with alt+F4

I did not enter into the details as i don't know about this XAML formatting method for windows forms.

thanks!

PD: also I found this dbase very slow for inserting, I measured less than 500 insertions per second for simple dictionary word string (<20 chars length), a int a float and another 5 char string, very disappointing!

cheers!

my PC is VS 2015, win 10 x 64, dual core G2200 the main screen is 1680 x 1050 (20 inch) another secondary screen of 19 inch on the left, configures my simple & cheap development PC.

andres

On Tue, May 23, 2017 at 3:16 AM, Josef Nemec notifications@github.com wrote:

I'm not sure I understand what the problem is. Does it mean that program window always stays maximized and you can't resize it or restore it from maximized state? Does it happen right after start? Can you share some screenshots? I also have Win10x64 with two screens and I fail to reproduce anything like you describe.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/JosefNemec/LiteDbExplorer/issues/7#issuecomment-303300759, or mute the thread https://github.com/notifications/unsubscribe-auth/ANCPcXOqQWopT7FUHxxrUjmQOBmPUtILks5r8nnJgaJpZM4Nilq8 .

-- ing. Andrés T. Hohendahl director PandoraBox www.pandorabox.com.ar web.fi.uba.ar/~ahohenda

-- ing. Andrés T. Hohendahl director PandoraBox www.pandorabox.com.ar web.fi.uba.ar/~ahohenda

JosefNemec commented 7 years ago

Thanks for suggestions. Could please create separate issues for each one of them, so we can keep better track of implementation and what features are request by people? Thanks.

JosefNemec commented 7 years ago

Fixed in 0.3