7 Dec
2012
7 Dec
'12
4:19 a.m.
Root conversation thread of Marc:
Le 2012-11-29 15:05, Rouslan Placella a ?crit :
(or table
On 28/11/12 13:53, Marc Delisle wrote:
> Rouslan Placella a ?crit :
>> On 27/11/12 17:55, Marc Delisle wrote:
>>> Hi Rouslan and list,
>>>
>>> I wonder whether this is a bug or a missing feature :) but
I noticed
>>> that in some situations, for example
following a foreign
link or picking
>>> a table from the output of
db_structure.php, the navi
panel does not
>>> position itself to the new table.
>>
>> Sorry, but I don't understand what you mean.
>
> Example 1:
> - in navi, click on sakila
> - in main, click on the Browse Action on the actor line
> - navi should show that actor is the current table
>
> Example 2:
> - in navi, click on sakila
> - in navi, under sakila, click on Tables then click on
inventory
> - in main, for inventory_id 1, click on the
film_id 1
> - now, in main you are seeing a row from film, but the navi
panel no
longer shows
that the current db is sakila
I see.
Well, it's not a bug. There is no such concept as a current db or other item) in the new navigation. The only
"current"
thing that
there is implemented is the current page in the db
pagination.
So if you
open something in a new tab, at least the db that the
item
displayed on
the page is associated with will be on the correct
page in the
navigation.
As far as implementing anything new goes, I think that the
issue with
MaxNavigationItems that is discussed in a different
thread
should be
addressed first, as it will change some of the
underlying logic
of the
navigation system.
Actually, Marc, would you please file this issue as a feature
request
and the other one as a bug on the tracker. Thanks.
I filed the two issues.
--
Marc Delisle
http://infomarc.info