EMULAB Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

The new forum is online, hope you enjoy it!

Pages: [1]   Go Down

Author Topic: Minor quirk - Taking user back to loaded dat folder  (Read 1746 times)

johnsanc

  • Member
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 5
  • Operating System:
  • Mac OS X 10.10.4 Mac OS X 10.10.4
  • Browser:
  • Chrome 43.0.2357.134 Chrome 43.0.2357.134
    • View Profile
Minor quirk - Taking user back to loaded dat folder
« on: 02 August 2015, 13:43 »

I noticed that clrmamepro always tends to take the user back to whatever folder contains the loaded DAT after any action with the profiler. For example I organize my DATs by type and system, so I have nested folders like "Console -> Nintendo - NES".

Lets say I want to add a few new DATs, so I navigate to the respective folder in the cmpro left nav, and drop it in. However as soon as thats done it takes me back to whatever folder contains the currently loaded dat. Is this intentional to take the user away from the last place they navigated to after they add a dat?
Logged


Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 106
  • Offline Offline
  • Posts: 3117
  • Operating System:
  • Mac OS X Mac OS X
  • Browser:
  • Safari 8.0 Safari 8.0
    • View Profile
Re: Minor quirk - Taking user back to loaded dat folder
« Reply #1 on: 02 August 2015, 19:19 »

most likely not intentional. I will look at it in the near future.
Logged

Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 106
  • Offline Offline
  • Posts: 3117
  • Operating System:
  • Windows NT 10.0 Windows NT 10.0
  • Browser:
  • Chrome 44.0.2403.130 Chrome 44.0.2403.130
    • View Profile
Re: Minor quirk - Taking user back to loaded dat folder
« Reply #2 on: 07 August 2015, 19:42 »

Well, I had a look at it and it is intentional ;-)
Everytime the tree/list is regenerated it tries to automatically navigate to the last used datfile...otherwise you always end at tree root...which is also not a good idea...

maybe I can have a look if I can redefine the "last used" to be either the last loaded or the one which was last used in an action (added, renamed)
Logged
Pages: [1]   Go Up
 

Page created in 0.101 seconds with 20 queries.

anything