Post subject: GB palette editor menu hidden?
Player (104)
Joined: 8/4/2013
Posts: 84
Location: Japan
old ver(1.6.1)GB Menu in palette editor now 1.8.4 GB Menu not palette editor where is palette edior menu
adelikat
He/Him
Emulator Coder, Site Developer, Site Owner, Expert player (3600)
Joined: 11/3/2004
Posts: 4739
Location: Tennessee
GB -> Settings -> Click the Palette button
It's hard to look this good. My TAS projects
Post subject: not Settings -> Click the Palette button menu
Player (104)
Joined: 8/4/2013
Posts: 84
Location: Japan
path setting Not wrong
adelikat
He/Him
Emulator Coder, Site Developer, Site Owner, Expert player (3600)
Joined: 11/3/2004
Posts: 4739
Location: Tennessee
Is that screenshot from the official release of 1.8.4? Because for me, there is Palette and Defaults buttons on that screen
It's hard to look this good. My TAS projects
Player (104)
Joined: 8/4/2013
Posts: 84
Location: Japan
default path not changing and path assignment not menu palette downldoad -> Emulator -> bizwahk -> 1.8.4 windows binary another path install bizhawk checkd not change path setting click to DualGameboy path menu mode dualGB?
Editor, Emulator Coder
Joined: 8/7/2008
Posts: 1156
It seems like you are writing about three bugs at the same time. It is very confusing. Let us talk about only one bug. So, let's ignore everything you already wrote. Now, using 1.8.4 I have set the GB palettes path. Bizhawk remembers it after I close it. It is used when I pick "Gameboy Settings > Palette..." and then pick load. The configured palette is remembered after I close the emulator. Everything is working perfectly. Which of those steps does not work for you?
Player (104)
Joined: 8/4/2013
Posts: 84
Location: Japan
zeromus wrote:
It seems like you are writing about three bugs at the same time. It is very confusing. Let us talk about only one bug. So, let's ignore everything you already wrote. Now, using 1.8.4 I have set the GB palettes path. Bizhawk remembers it after I close it. It is used when I pick "Gameboy Settings > Palette..." and then pick load. The configured palette is remembered after I close the emulator. Everything is working perfectly. Which of those steps does not work for you?
1 Bizhawk setting directpath gameboy and dual gameboy palette path(not use 2byte lang folder) 2 Bizhawk reboot 3 GB menu->settings click not palette menu GB rom and GBC rom all not palette menu
Editor, Emulator Coder
Joined: 8/7/2008
Posts: 1156
Which URL did you download bizhawk from? Which version are you testing now? Please delete your bizhawk config.ini file and try to find the 'Palette...' button in the GB config. Do not set a custom path. Does it work? Now, set the custom path to c:\ ; Does the 'Palette...' button appear? Now, set the custom path to what you want; Does the 'Palette...' button appear?
Editor
Joined: 3/31/2010
Posts: 1466
Location: Not playing Puyo Tetris
I checked with SVN Build 8151 and I set my Pallet Path to something that's obviously not default. It worked fine for me.
When TAS does Quake 1, SDA will declare war. The Prince doth arrive he doth please.
Player (104)
Joined: 8/4/2013
Posts: 84
Location: Japan
zeromus wrote:
Which URL did you download bizhawk from? Which version are you testing now? Please delete your bizhawk config.ini file and try to find the 'Palette...' button in the GB config. Do not set a custom path. Does it work? Now, set the custom path to c:\ ; Does the 'Palette...' button appear? Now, set the custom path to what you want; Does the 'Palette...' button appear?
download bizhawk url(prererease file intalling) http://sourceforge.net/projects/bizhawk/files/BizHawk/BizHawk%201.8.4.zip/download deleted config.ini try path not setting use GB menu->setting clickd not palette button palette path c:\ setting and reboot not GB settings palette button palette path(delete folder space [bizhawk 1.8.4] to [bizhawk1.8.4]) C:\game\BizHawk1.8.4\Gameboy\Palettes setting direct path and reboot not GB setting pallete button
Editor, Emulator Coder, Site Developer
Joined: 5/11/2011
Posts: 1108
Location: Murka
AmaizumiUni wrote:
zeromus wrote:
Which URL did you download bizhawk from? Which version are you testing now? Please delete your bizhawk config.ini file and try to find the 'Palette...' button in the GB config. Do not set a custom path. Does it work? Now, set the custom path to c:\ ; Does the 'Palette...' button appear? Now, set the custom path to what you want; Does the 'Palette...' button appear?
download bizhawk url(prererease file intalling) http://sourceforge.net/projects/bizhawk/files/BizHawk/BizHawk%201.8.4.zip/download deleted config.ini try path not setting use GB menu->setting clickd not palette button palette path c:\ setting and reboot not GB settings palette button palette path(delete folder space [bizhawk 1.8.4] to [bizhawk1.8.4]) C:\game\BizHawk1.8.4\Gameboy\Palettes setting direct path and reboot not GB setting pallete button
So when using 1.8.4 you never see a palette button in GB settings, no matter what you change?
Editor, Emulator Coder
Joined: 8/7/2008
Posts: 1156
It sounds like your computer is the only one in the world with this problem. Can you try it on another computer? I think it has to do with fonts, desktop enhancements, DPI, etc. Something is making two buttons disappear. I'm sure you've tried resizing that window, right? It has a size grip in the corner.
Player (104)
Joined: 8/4/2013
Posts: 84
Location: Japan
hegyak wrote I checked with SVN Build 8151 and I set my Pallet Path to something that's obviously not default. It worked fine for me. _________________ after build to try natt worte So when using 1.8.4 you never see a palette button in GB settings, no matter what you change? _________________ bizhawk ver 1.7.4 not palette button 1.6.1 use palette editor on GB menu zeromus wrote It sounds like your computer is the only one in the world with this problem. Can you try it on another computer? I think it has to do with fonts, desktop enhancements, DPI, etc. Something is making two buttons disappear. I'm sure you've tried resizing that window, right? It has a size grip in the corner. _________________ Japanese windows using another user same symptoms
Editor, Emulator Coder
Joined: 8/7/2008
Posts: 1156
OK, I can fully explain this problem. Our forms were all set to AutoScaleMode.Font. This means that the dialog is resized according to the font size used for the dialog. .Net uses a 9pt font on Japanese systems (vs a 8.25pt font on others) by default. Therefore, the dialog will be resized for japanese users to fix the mismatch between developers and users font sizes. This should work. However, there are bugs in .net which make certain dialogs malfunction. In our case, for the record, it's the use of Bottom and Right Anchor styles. I tried to fix this by various font substitution methods, but the problem seems to be the use of a 9pt font, and there's no way around that short of hacking .net. Therefore, to fix it, we have chosen to suppress the auto-sizing. The work needs to be done for each dialog, so if you encounter similar problems in other dialogs, we'll need to fix them also. I suggest that you keep an english windows XP VM for testing things like this, if you're going to be using english language software. This particular GB config problem was fixed, I hope, by r8154.
Player (104)
Joined: 8/4/2013
Posts: 84
Location: Japan
Investigation Thank you Since hurry do not wait for the next version
Player (144)
Joined: 7/16/2009
Posts: 686
zeromus wrote:
Therefore, to fix it, we have chosen to suppress the auto-sizing. The work needs to be done for each dialog, so if you encounter similar problems in other dialogs, we'll need to fix them also.
I've had a look, and this fixes some of the dialogs I'm not seeing properly too. I could go over the ones that it fixes for me (the TAStudio dialog, among others) and commit those? I have it extra easy because it fixes them in-editor, so I don't even have to compile or open the windows to do it.
Editor, Emulator Coder
Joined: 8/7/2008
Posts: 1156
the general rule is: you must not edit dialogs while using a non-96 DPI, otherwise your visual studio editor will emit other code which will break the scaling. Namely, an AutoScaleSize will change from 13 to 12 or something like that. However, since what we're doing here is _disabling_ the auto-scaling, it should be benign. Please go ahead and fix whichever dialogs you need to, as long as how youre fixing it is precisely what r8154 did.