4027 replies to this topic

[Wylte]

In 10.7.0 the properties bar on the right does not have a  vertical scroll bar for showing long content.

 

Try resizing your window vertically - you get no scrollbar - but if you resize horizontally you get a horizontal scroll bar.

 

Any chance you can add a vertical scroll bar for us that have small screens?

Similar issue in rev129 (fa410b5):

When adjusting the split between properties and layers, the properties section creates a vertical scroll bar at a set height, so it doesn't scroll down to all of the content.  Horizontal behavior is accurate.

 

Have screenshots if it can't be reproduced, just can't paste them in my reply

[wiesshund]

 

In 10.7.0 the properties bar on the right does not have a  vertical scroll bar for showing long content.

 

Try resizing your window vertically - you get no scrollbar - but if you resize horizontally you get a horizontal scroll bar.

 

Any chance you can add a vertical scroll bar for us that have small screens?

Similar issue in rev129 (fa410b5):

When adjusting the split between properties and layers, the properties section creates a vertical scroll bar at a set height, so it doesn't scroll down to all of the content.  Horizontal behavior is accurate.

 

Have screenshots if it can't be reproduced, just can't paste them in my reply

 

 

WORKS

 

WORKS NOT

[toxie]

I actually looked into both two days ago, but am clueless, none of my workarounds worked.. Fuzzel to the rescue..

[fuzzel]

Yes I know...this is one of these Win32 mysteries I couldn't solve until now. I'll take another look..

[wiesshund]

I actually looked into both two days ago, but am clueless, none of my workarounds worked.. Fuzzel to the rescue..

Workround

 

i ripped the options pane out of the editor

It behaves now

 

Ok not a solution, but it saves someone a headache

[Wylte]

 

I actually looked into both two days ago, but am clueless, none of my workarounds worked.. Fuzzel to the rescue..

Workround

 

i ripped the options pane out of the editor

It behaves now

 

Ok not a solution, but it saves someone a headache

 

I like having them attached, but just squishing the layers when I need to see the bottom properties works for me

[wiesshund]

 

 

I actually looked into both two days ago, but am clueless, none of my workarounds worked.. Fuzzel to the rescue..

Workround

 

i ripped the options pane out of the editor

It behaves now

 

Ok not a solution, but it saves someone a headache

 

I like having them attached, but just squishing the layers when I need to see the bottom properties works for me

 

I do too

but i hate having to smoosh layers up and down

 

Probably would not be so bad, but i have OULD (Obsessive Use of Layers Disorder)

[fuzzel]

I actually looked into both two days ago, but am clueless, none of my workarounds worked.. Fuzzel to the rescue..

Fixed! And on top of this I changed the other floating dialogs (toolbox and layers) to behave in the same way. If you resize these dialogs the controls of the dialogs will be also resized. The later is still a WIP because of so many elements

[supered]

If we are looking at helping vpx support issues in v10.7....im constantly seeing the DISPLAY ID playfield issue that new users are always running into (windows displayIDs change on many systems).  I've mentioned before v10.6 earlier builds used primary(main display) monitor for playfield so was never a problem...that changed later in 10.6 and i regularly see daily issues with the playfield showing on peoples BG or DMD.  There's a bunch of workarounds,  reboots sometimes fix.. i even wrote a util that updates the VP registry based on main/primary monitor. but its a big support headache.
 
I can compile a new b2s that uses xpos/ypos instead of Windows DISPID because b2s also screws up for many at same time because of dispid#.,  but vpx is still an issue for many.    
 
possible solutions.   a commandline -primary to force vpx to use primary monitor for playfield.  Or a checkbox in video settings that has 'use primary display' instead of using a display#.

I assume it’s a nasty window10 problem ?!?
We have the same issue with our corporate software that uses multimonitors. You never know which one is nr 1 after reboot.

Thank God my cab is still windows 7. Doesn’t have that fancy monitor ID issue....?!?


Verzonden vanaf mijn iPhone met Tapatalk

[wiesshund]

Strange crash, that i can reproduce, but do not know if it is the beta or the table

 

Selecting a group of lights on the backdrop

LED score lights, so lot of little pieces

 

just changing values, but did not seem to specifically care what value

1st launch to test change ok, return to editor to change more, fall off value in this crash
launch and poof dead

Crash report VPX rev136 (a4822e3)
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:1B3F6D9E
Attempt to read from 0x00000004
Thread ID: 0x1D5C [7516]

Call stack
==========
1B3F6D9E  (0x2559E87C 0x259A0A28 0x00000000 0x00000000)
1B3F61DC  (0x299CD8A0 0x00000000 0x00000001 0x299cd8a0)
1B3F609C  (0x00000000 0x00000001 0x299CD8A0 0x1b3f6048)
0F27D49D  (0x27BFCF50 0x00000000 0x00000001 0x299cd8a0)

Environment
===========
Date/time: 24/4/2021, 00:42:20:31
Number of CPUs: 8
Processor type: 586
System: Windows 10 (10.0 19042)

Memory status
=============
Total Reserved: 218060K (212M) bytes
Total Commited: 967816K (945M) bytes
Total Free: 3008364K (2937M) bytes
Largest Free: 2094912K (2045M) bytes

Registers
=========
EAX=259AF61C EBX=2559C768 ECX=6A271468 EDX=1078EC68
ESI=259AF61C EDI=00000000 EBP=00000000 ESP=196EFC08 EIP=277E0F62
FLG=00010202 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B


Failed to save minidump.

[toxie]

Which table? So that we can try to repro.

[wiesshund]

Which table? So that we can try to repro.

close encounters

[jipeji16]

Hi super Guys !!!

I just tried VP 10.7 beta, and it runs well our Alpha of Alien... That's already a very good thing

 

But i had two problems :

 the first is that i didn't find the 1080x1920 (windowed fullscreen) option, so if i try another thing (necessarily the wrong choice), the only way for me to get again this parameter is to come back to vpx 10.6 and put this résolution again. when i run the vp 10.7 it's memorised.

the second is more an asking, could we have a button to reinitialize the layers/properties position. I say that because i lost the layers window (no more tabs at the bottom of the property window to get the layers). Another time to come back to this little bug, i had to come back to vpx 10.6 and open again the 10.7.

 

And maybe a little late comment about the multiplication of tabs for editing objects... the old way to see all parameters was very effective i think. Perhaps, in the future, could we move and open the tabs to see all in one time verticaly, or another way to come back to the old presentation.

 

Big thanks another time to all of you for your hard work !!!!!

 

JPJ

[wiesshund]

 

But i had two problems :

 the first is that i didn't find the 1080x1920 (windowed fullscreen) option, so if i try another thing (necessarily the wrong choice), the only way for me to get again this parameter is to come back to vpx 10.6 and put this résolution again. when i run the vp 10.7 it's memorised.

 

That option should be present, IF your OS is rotated, since that is a rotated resolution

If your OS is not rotated, it wont present it to you as a valid resolution, though you could force it in regedit

 

Computer\HKEY_CURRENT_USER\SOFTWARE\Visual Pinball\VP10\Player

 

change values Width and Height
click DECIMAL before typing in your value unless you are going to type it in as hexadecimal

 

10.6 and 10.7 have different editor layout capabilities

if you find you lose some parts when hopping back and forth, you can delete this key and reopen vpx editor

 

Computer\HKEY_CURRENT_USER\SOFTWARE\Visual Pinball\VP10\Editor\Dock Windows

[jipeji16]

Thanks Wiesshund !!!! I'll try this

 

I m in Portrait Mode...

 

Thanks again for your quick answer

 

JPJ

[goblindriver]

I can confirm windowed fullscreen resolutions don't show up on portrait monitors after any settings get written to the registry. I've been manually putting them in like what weisshund mentioned above.

[toxie]

Do you guys have any clue with which revision/date this roughly started happening?

[wiesshund]

Do you guys have any clue with which revision/date this roughly started happening?

 

give my a while to do some downloading

but they are definitely gone.

 

I have gone back to build
VPinballX 123-f654ed

and it is messed up there too

you could just let us type in the values for non full screen?
course i'd like to type in the x and y window pos too

I am back as far as VPinballX-10.7.0-102-88f2dd8

still not good

build 4356 which is prior to the new revision numbers from github works
the full sized non fullscreen portrait res shows up right between portrait and landscape

 

more downloading

VPinballX  f9a3765
Still no good

ok i went all the way back to  3be1932

master

 

All bad in regards to rotated OS and being offered the correct resolution, except when forcing exclusive fullscreen

Edited by wiesshund, 25 April 2021 - 07:31 AM.

[wiesshund]

I am not sure if this is a bug or not but
Customkey settings do not appear to want to save
but you can put them in the registry and then they stick

 

JoyCustomKey1 through 4

 

But if you try to use them in a table
if keycode = JoyCustomKey1 

or JoyCustom1 if you set it to a controller button

 

you just get an error that JoyCustomKey1 or JoyCustom1 is undefined

 

does not seem you should have to declare a key that exists in the keymapper?
we dont have to declare lockbarkey etc.

 

 

[fuzzel]

rev153 is up:

 

- resizing properties will also scale the internal property elements of the dialog

- reduce flickering when resizing/zooming table view

- fix vertical/horizontal scrollbar handling for toolbar, property, layer, image/material manager

- fix F1-press crashing VPX (now shows About dialog)

- deactivate new plunger behavior as default setting

- fix ogg/mp3 volume level