is there some interface-function that returns the path to the configuration-folder? if not: can i somehow determine if it's a normal or portable foobar installation?

namespace core_api {
    const char * get_profile_path();
    bool is_portable_mode_enabled();
};

Quote from: jeanpaulrichter on 2015-08-30 19:10:14

is there some interface-function that returns the path to the configuration-folder? if not: can i somehow determine if it's a normal or portable foobar installation?

foobar2000\SDK\core_api.h:

Code: [Select]

namespace core_api {
    const char * get_profile_path();
    bool is_portable_mode_enabled();
};

- if i use the old, simple preferences_page_v2 (i am not using atl) for a preference dialog, can i still support the "ok/cancel/apply"-buttons? and if yes how? i know this is pretty old, but i am using https://github.com/msquared2/columns_ui as a basis atm and that has a very old sdk. if someone has something newer that works i would be very very thankful

the new preferences dialog needs at least the v1 SDK. looking at the SDK download page, v1.1 (2011-03-11) is still available and i'm pretty sure i was able to make columns UI and that SDK compile with minimum fuss. compiling really is the limit of my capabilities though. i can't help with how to implement... anything.

Quote from: marc2003 on 2015-08-30 20:37:16

the new preferences dialog needs at least the v1 SDK. looking at the SDK download page, v1.1 (2011-03-11) is still available and i'm pretty sure i was able to make columns UI and that SDK compile with minimum fuss. compiling really is the limit of my capabilities though. i can't help with how to implement... anything.

thanks, i will have a look at it. (btw: i am amazed how fast you guys answered: i half expected this forum to be kind of dead ^^)

preferences_page_instance::ptr instantiate(HWND parent, preferences_page_callback::ptr callback)

- when i create a playlist from a podcast-feed i atm use hint_async to set information about items and it works fine. i am just not really sure what a hint is, when it should be used and when foobar uses it ? =) btw: how can i set the "Length" of a track with a hint?

Quote from: jeanpaulrichter on 2015-08-30 19:10:14

- when i create a playlist from a podcast-feed i atm use hint_async to set information about items and it works fine. i am just not really sure what a hint is, when it should be used and when foobar uses it ? =) btw: how can i set the "Length" of a track with a hint?

foobar2000 caches metadata about tracks (not files!) for faster access. The cached metadata includes the file size, the file modification time, the duration of the track, used-defined tags and technical information (codec, sample rate, bit depth, ...). foobar2000 uses the file size and file modification time to detect when it needs to reload the cached information. When a reference to a new track (a metadb_handle) is created the cache contains no information about the track. Normally foobar2000 would have to access the file to read the information into the cache. The hint function exists to populate the cached information for a track without accessing the file. This is used when reading FPL playlists since they contain a copy of the cached information. Note that you cannot use the hint mechanism to override the cache information. When the user request to reload the information from the track foobar2000 will replace the cached information.

The process_locations or process_locations_async functions are the recommended way to get the metadb_handles for a file (or more generally a list of paths). The handle files with multiple tracks as well as playlist files. These functions also display an "annoying" dialog so the user can cancel the operation if it gets stuck or takes longer than expected.

Nonetheless there are valid cases when you need to read the information directly from the file. See the thread foobar2000 v1.3 upcoming changes for details. It also provides a code snippet showing how to do this. By the way you can get the number of tracks in a file using the input_info_reader::get_subsong_count method.

For the implementation of the preferences_page_v3::instantiate method you need to do the following. Create a child window using the given window handle as the parent window. The most convenient way to do this is to create a non-modal dialog from a dialog template. You should use the WS_CHILD and WS_EX_CONTROLPARENT window styles. Store the callback reference for use in you window procedure. Use it to notify the preferences window when the state of your preferences window changes, i.e. when the enabled state of the apply button needs to be updated. The instantiate method needs to return an implementation of the preferences_page_instance interface. foobar2000 uses this to get the window handle for your preferences page and to query the state of the Apply button.  It also uses it to notify you when you need to save or reset the configuration data, i.e. when the user clicks Apply, OK or one of the Reset buttons. The intention is that the user can edit the value on the preferences page but that the changes do not take effect until the user clicks Apply or OK.

A common pitfall in this scenario is the lifecycle management of your objects. The window procedure and the preferences_page_instance object will need some shared data. You need to keep this shared data alive until both the window and the preferences_page_instance have been destroyed to avoid dangling pointers. Look up the difference between the WM_DESTROY and WM_NCDESTROY window messages if you don't already know it! You should also avoid leaking memory. The WTL based helper classes take care of these subtleties.