|
|
Post by JarheadHME on May 19, 2014 22:39:57 GMT
|
|
|
|
Post by raynebc on May 19, 2014 23:26:59 GMT
I've never seen that behavior before. Just to rule out an issue, could you rename/delete the eof.cfg file so it starts with all default settings? Which release of EOF is this? Was this the first time you've used EOF on that laptop? What OS is it? It could be some strange compatibility issue between Allegro and your setup, but it may be worth setting the compatibility settings for the EOF executable to something older (ie. Windows XP) to see if that helps.
|
|
|
|
Post by JarheadHME on May 20, 2014 2:10:10 GMT
welp deleting the eof.cfg worked :\ no idea why. It was r1337, yes it was the first time on that laptop, and it was Windows 7 64x
|
|
|
|
Post by raynebc on May 20, 2014 5:26:50 GMT
So it's working fine now? If you happen to still have the eof.cfg file as of when the problem occurred, could you send me its contents? Or if you change your preferences one at a time and notice that a specific one causes the problem to start happening again, let me know.
|
|
|
|
Post by JarheadHME on May 21, 2014 20:28:04 GMT
heres the contents of the old eof.cfg dl.dropbox.com/s/nyax7z5h1xnista/eof.cfgJust out of curiosity... songs_path = Z:\Documents\JaretFS\Programs\EOF\ eof_path = Z:\Documents\JaretFS\Programs\EOF\Avenged Sevenfold - M.I.A\ ogg_path = D:\wtfp1\ db_path = D:\Retaliator\ midi_path = C:\Users\Alucard0\Desktop\ ps_path = D:\Games\Phase Shift\phase_shift.exe ps_songs_path = Z:\Documents\JaretFS\Phase Shift Music\ would it make it break that all of these paths don't exist on my laptop? |
|
|
|
Post by raynebc on May 21, 2014 20:36:23 GMT
My best guess is that the laptop didn't like the display size you were using for EOF on your other computer. If you had time to kill, you could verify if this is the case by restoring the eof.cfg file that wasn't working, and edit it before launching EOF so that these default values are included:
[display]
display_mode = 0
eof_screen_width = 640
note_auto_adjust = 1
software_mouse = 0
true_color = 1
Edit: I don't think those paths would have anything to do with it, especially if the problem happened right when you start EOF and before you try to open any files.
|
|
|
|
Post by JarheadHME on May 21, 2014 20:59:13 GMT
yeah apparently that was it, cause i restored it an edited it, ah well, that was time wasted.
|
|
|
|
Post by Inf4mousKid on Jun 9, 2014 22:45:48 GMT
it might be wise to tell people this in a read me file so they know about this in the future
|
|
|
|
Post by vandorb12 on Jun 10, 2014 1:27:58 GMT
it might be wise to tell people this in a read me file so they know about this in the future This seems to be a very rare case. IMO, I don't think this bug deserves to be in a readme. |
|
|
|
Post by raynebc on Jun 10, 2014 16:47:05 GMT
I'm going to try to add more handling for this, but I agree it's not common for people to run into this issue.
|
|
|
|
Post by Inf4mousKid on Jun 28, 2014 17:05:30 GMT
You know if may add on to this. I have this similar issue on my computers. As it turns out my computer at home has different graphics settings and if I put eof to its max size it will encompass the entire screen but this computer I'm on now (grandma's house) has a much bigger monitor so eof just has a bigger size.
I know I'm not one to suggest things like this but I think it would be good to prompt a user on first launch about adjusting eof's resolution. Update: At least until the issue can be worked on a little more
|
|
|
|
Post by raynebc on Jun 28, 2014 17:32:57 GMT
On first launch, EOF's config file is not present, so it goes to all default settings, which should work on pretty much any computer. EOF won't have a way to easily tell when you're running another computer's configuration file on a computer, so it can't prompt to resize the screen. I'm going to just try to have it make sure that if the window size defined in the config file can't be set, it will try to revert to the default instead.
|
|
|
|
Post by Inf4mousKid on Jul 3, 2014 1:32:59 GMT
it will try to revert to the default instead. sound like a plan and I like that |
|
|
|
Post by raynebc on Jul 3, 2014 16:25:51 GMT
After testing, I couldn't find this is an issue with the window size. If EOF can't set the size, it reverts to the default of 640x480. I tested this by editing the eof.cfg file to use a width 1 pixel wider than my OS screen resolution, and when I opened EOF, it reverted to 640x480 as expected. Without you testing each cfg file change one at a time, I'm not sure there will be an easy way to tell which option was causing the problem.
|
|
|
|
Post by Inf4mousKid on Jul 4, 2014 4:58:18 GMT
After testing, I couldn't find this is an issue with the window size. If EOF can't set the size, it reverts to the default of 640x480. I tested this by editing the eof.cfg file to use a width 1 pixel wider than my OS screen resolution, and when I opened EOF, it reverted to 640x480 as expected. Without you testing each cfg file change one at a time, I'm not sure there will be an easy way to tell which option was causing the problem. Ah, programming thou arth a heartless bitch! |
|
